Kadir Türker Gülsoy

Recent Posts

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

New Updates for Teams

Oct 31, 2016 by Kadir Türker Gülsoy

Routing To Teams via Escalations

  • You can now configure escalation steps to route to teams.
  • If an escalation step is configured to route to a team, the routing rules of the specified team will be applied while determining the alert recipients to notify.
  • Escalations that belong to a team can also be configured to route to another team.

Routing to Teams via Schedules

  • From now on, if a schedule rotation includes a team as participant, the routing rules of the specified team(s) will be applied while determining who is on-call for that time period.
  • Prior to October 31, 2016, all members of the participant team(s) were on-call in case of such a configuration.
  • Existing schedules that include team participants will keep their current behavior unless they're not updated.

No One as Schedule Participant

  • You can now configure your schedule rotations and overrides to include No-One as the participant.
  • No user will be on-call for the specified time range, if No-One is specified as the participant.

New Product Updates

Sep 20, 2016 by Kadir Türker Gülsoy

Team Routing Rules

  • You can now add multiple routing rules for a single team. You can also configure different alert based conditions and time restrictions for each routing rule.
  • You can configure any escalation or schedule of the team within team routing rules. You can also configure a routing rule not to notify anyone via selecting No One option.
  • When an alert is routed to a team (during alert creation or via Add Team action), the first matching routing rule will be used to determine which team schedule or escalation should be used to add recipients. If the matching rule routes the alert to No One, all team members will gain visibility to the alert but no one will be notified.
  • You can refer Teams for further information.

Team Segmentation

  • Integrations can now be assigned/restricted to particular teams. Team admins without account owner/admin rights can also create integrations for their teams.
  • An existing global integration, escalation or schedule can only be assigned to a particular team by an account owner/admin.
  • Any alert created via integrations that are assigned to a particular team are routed to the team that this integration is assigned to. In other words, a team restricted integration can not have any recipient or any team other than the assigned team to route the alert.
  • Team restricted integrations can execute an alert action only if the alert is visible to the team that the integration is assigned to.
  • A team restricted API integration can only access the following API domains with the following restrictions:
  • Alert API
  • Team API: Team should be the owner of integration.
  • Escalation API: Escalation should be restricted to the same team with the integration that sends the request.
  • Schedule API: Schedule should be restricted to the same team with the integration that sends the request.
  • Schedule Override API: Schedule should be restricted to the same team with the integration that sends the request.
  • Integration API: Target integration should be restricted to the same team with the integration that sends the request.
  • An outgoing team-restricted integration can not send callbacks for an alert that is not visible to the team that the integrations is assigned to.
  • You can refer Team Segmentation for further information.

New Features & Updates

Aug 22, 2016 by Kadir Türker Gülsoy

Alert Count Based Notification Policies

  • You can now configure Notification Policies to delay notifications unless the deduplication condition that you specified is satisfied.
  • If an alert matches with a Deduplication Correlated Notification Policy, notification flow will not be started even if there are specified recipients or teams.
  • When the deduplication count or deduplication occurrence rate satisfies the condition you specified, alert notifications flow will be started.
  • You can refer Notification Policies for further information.

Auto Restart-Notifications Policies

  • You can configure an Restart-Notifications Policy to hit after the time that you specified, if the alert content conditions and time restrictions are satisfied.
  • When an Auto Restart-Notifications Policy hits, the notifications flow of the alert will start from the scratch and recipients will start getting notifications even if the alert is acknowledged or recipients had already become aware.
  • You can refer Alert Policies for further information.

Behavioral Option for Escalation Repeating

  • Escalations now have an option in addition to the repeat after time. If this option is selected, while an escalation is repeating and the relevant alert is still open, all states of the alert that prevents a recipient from being notified will be reverted.
  • In other words, even if the alert is acknowledged or a recipient from an escalation viewed the details of the alert via any of the OpsGenie apps, the recipients of the escalation rules will be notified on the next repeat turn if the option to do so is selected.

Re-Notify Policy Deprecation

  • Re-Notifying options of Notification Policies are deprecated by now. Already configured notification policies with re-notify options will continue working until the removal date; however, notification policies can not be configured to include a re-notify option.
  • Already configured re-notify options of notification policies should be replaced with alternative configurations like an escalation or an auto restart-notifications policy until November 25, 2016.After that time, re-notify options will be completely removed.
  • You can refer Migration Guide for Deprecated Re-Notification Policies for guidance.

Other Updates

  • Account owners can now setup a reminder to receive a reminder email for the number of users left that can be added for your billing plan. When the remaining number of available user slots decrease to the threshold that you configured, account owners will receive a reminder email. Account owners can configure a reminder via Billing page.