Kadir Türker Gülsoy

Recent Posts

API v1 Will No Longer Be Available as of June 30, 2018

Mar 14, 2018 by Kadir Türker Gülsoy
  • API v1  was deprecated on May 2017 when Rest API was released. As of June 30, 2018, API v1 is going to be inaccessible for all customers (Currently, only the customers that were signed up before October 2017 have access to API v1).
  • You can refer here for the guideline to migrate to Alert Rest API.
  • You can refer here for the guideline to migrate to Heartbeat API.
  • If you're using Script Proxy for Maridupdating your Marid to the latest version will automatically route your API requests to the new Rest API.
  • If you're using Lamp to access the Alert API, updating your Lamp to the latest version will automatically route your requests to the new Rest API.

New Alert & Notification Policies

Jan 30, 2018 by Kadir Türker Gülsoy
  • Policies are revised and redesigned in terms of functionality and UX. 
  • Modify Policies are replaced with Alert Policies by merging the Teams and Recipients fields into a single Responders field that can include both teams and users. Alert Policies can be configured and assigned to specific teams. Team admins or team members with the related right can also create and configure Alert Policies for their own teams.
  • Suppress, Delay, Alert Count, Auto Restart and Auto Close Policies are replaced with Notification Policies so that the same functionalities can be achieved via a single configuration type. 
  • Notification Policies are now team-segmented configurations. Team admins or team members with the related right can create and configure Notification Policies for their own teams.
  • Customers that were signed up before January 29, 2018 1PM UTC are able to configure and work with the old policies, but meanwhile  they can create and configure New Alert & Notification Policies. Account owners and admins can explicitly switch their accounts to use new policies while creating alerts.
  • Maintenances can now be configured and assigned to specific teams. Team admins or team members with the related right can also create and configure maintenance for their own teams. A team maintenance can only enable/disable team policies and team integrations. 

Upcoming Updates to the Visibility Constraints of Escalations and Schedules

Jan 12, 2018 by Kadir Türker Gülsoy
  • Effective from January 17, 2018 2PM UTC, the visibility constraints of the schedules and escalations will be updated for the sake of performance improvements. Alert notifications flow will not be affected in any manner. The update will affect the following configuration scenarios:
    • Scenario 1: ... -> Escalation 1 -> Schedule 1 -> Escalation 2 -> ...
    • Scenario 2: ... -> Schedule 1 -> Escalation 1 -> Schedule 2 -> ...
  • Scenario 1: 
    • If Escalation 1 or Schedule 1 is assigned to a team that the user is member of, there will be no behavioural update. 
    • If a user is referenced by Escalation 2 but is not referenced by Escalation 1, Escalation 1 will not be displayed to the user on My Profile > Profile -> Escalations section.
  • Scenario 2:
    • If Schedule 1 or Escalation 1 is assigned to a team that the user is member of, there will be no behavioural update.
    • If a user is referenced by Schedule 2 but is not referenced by Schedule 1, Schedule 1 will not be displayed to the user on My Profile > Profile -> Schedules and Who Is On Call > My Schedules sections.

Outgoing Integration Trigger Updates

Dec 15, 2017 by Kadir Türker Gülsoy
  • OpsGenie now sends outgoing integration callbacks when an alert is routed to a new team via escalations or schedules.
  • Previously, outgoing integrations were triggered for new teams if and only if they were added via Add Team action.
  • You can refer Outgoing Integration Triggers for further details.

Team Heartbeats

Sep 27, 2017 by Kadir Türker Gülsoy
  • Heartbeats and Heartbeat Integrations can now be assigned to specific teams.
  • Team admins can create and configure heartbeats and heartbeat integrations for their own teams. Authorization constraints of the heartbeats are the same as escalations, schedules and integrations.
  • When a team heartbeat is expired or pinged, the heartbeat integration that is owned by the same team executes its related alert action.
  • You can refer to Heartbeat Monitoring for further details.

Updates on the User Structure and Users Page

Jun 7, 2017 by Kadir Türker Gülsoy
  • Users Page is re-designed with a new look & feel. You can refer to Managing Users for further information and guidance.
  • Users can now be searched and filtered via search queries. You can refer here for further information.
  • Custom roles can now be configured with the following additional rights:
    • Managing Billing / Subscription
    • Editing Contacts
    • Editing Profile
  • Observer role is now available as a new default role. Observers are read-only users that can only receive notifications for Mass Notification events. You can refer here for further information about user roles.

Latest Updates

Mar 6, 2017 by Kadir Türker Gülsoy
  • Escalate to Next action is added as an option to alert voice notifications. If there is any ongoing escalation flow for an alert, Escalate to Next action will be available as an option. You can refer Voice Notifications for further information. 
  • Matches Regex condition operation is now available for input fields with List types for the conditions of integration actions, alert & notification policies, team routing rules and notification rules. If any element of the input field with List type matches the given regular expression, the condition will be satisfied.

Custom User Role Updates

Jan 3, 2017 by Kadir Türker Gülsoy
  • Users that are not an admin or owner can now be granted with the right to update active or planned Maintenance Policies.
  • You can refer Users and Roles for further information about custom user roles.

OpsGenie Android & iOS Mobile Updates

Dec 19, 2016 by Kadir Türker Gülsoy

OpsGenie Android v2.2.7 and OpsGenie iOS v2.2.2 are now available.

  • On Who Is On-Call page, you now have the option to display only your schedules as well as all schedules within your organization.
  • You can now filter the displayed schedules in Who Is On-Call page via free-form text search.
  • While adding an override to a particular schedule via Who Is On-Call page, you can now specify which rotations of the schedule it should apply to. Previously, overrides were applied to all rotations of the schedule.
  • You can now specify an exact time range while adding an override to a particular schedule via Who Is On-Call page.
  • When you tap/navigate into our short link (opsg.in) from anywhere within your device, OpsGenie application is launched. If you click the provided alert link within your SMS notification, the application is now redirected to the related alert.
  • Add Recipient and Add Team actions are now merged under the name "Add Recipient". You can add a user, an escalation, a schedule, a group or a team to an existing alert to be notified via Add Recipient action.
  • You can upgrade your mobile apps to the latest versions via Apple App Store or Google Play Store.

Ability to Configure Read-Only Access to API

Nov 22, 2016 by Kadir Türker Gülsoy
1 2