Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How can you test your notifications when your on-call roster starts?

Every Opsgenie team has an on-call roster with their team members. As a team member, when you start your on-call week, how can you be sure that your notifications are setup correctly? This is essential as you don't want to miss any calls from a potential high priority alert.

Opsgenie's REST API allows both creating and deleting an alert.

Here is an example of how you can generate a test P1 alert:

curl -X POST \
-H "Content-Type: application/json" \
-H "Authorization: GenieKey $API_KEY" \
-d \
\"message\": \"Notification test\",
\"alias\": \"notification-test-<random_id>\",
\"description\":\"Test notification\",
{\"name\":\"$TEAM_NAME\", \"type\":\"team\"}

You can place this in a Bamboo plan or any build tool that can schedule this script to run after your on-call roster starts. Eg. run every Monday at 9 AM.

When this build is run, the person on-call on that week would receive a phone call, which confirms the person's notifications are setup correctly.

This method can also be used to ensure your other types of notifications as Slack are working properly every week.

As a best practice, it would be a good idea to clean up this test alert after a few minutes in the same build. So this alert won't come up in any of your reports.

Here is how you can delete the test alert created earlier:

curl -X DELETE "$id?identifierType=id" \
-H "Authorization: GenieKey $API_KEY"

 Hope this brings confidence to the person coming into the roster schedule.


I would find it very useful if there was test button that could be used to verify a user has their notification information entered correctly.

Like # people like this

Pager Duty has a simple button where you can quickly test all the plumbing is in place.

Like # people like this

You can also create an alert from the Alerts page as per the official docs for creating a manual alert.


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events