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!


VMware Operation Manager Integration with OpsGenie


I was wondering if anyone has been successful at integrating vROPS with Opesgenie using the built-in webhook method supplied by vROPS. 

I'm able to create tickets using curl from the vROPS appliance so the API key and headers are good.  For some reason none of the alerts are reaching Opsgiene from vROPS itself.

Any ideas?



1 answer

0 votes
Nick H
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 29, 2022

Hi @xcloete ,

I'm not sure we have any sharable examples of integrating Opsgenie with vROPS. But customers will typically leverage either an Email integration or API integration to integration with 3rd party systems if Opsgenie does not provide a prebuilt integration. 

Our Alert API documentation might also be helpful with knowing what headers are needed in order to get this potentially working! There's a sample request example from that page using the Create Alert API, and what headers are needed:

curl -X POST

    -H "Content-Type: application/json"

    -H "Authorization: GenieKey eb243592-faa2-4ba2-a551q-1afdf565c889"



    "message": "An example alert message",

    "alias": "Life is too short for no alias",

    "description":"Every alert needs a description",


        {"id":"4513b7ea-3b91-438f-b7e4-e3e54af9147c", "type":"team"},

        {"name":"NOC", "type":"team"},

        {"id":"bb4d9938-c3c2-455d-aaab-727aa701c0d8", "type":"user"},

        {"username":"", "type":"user"},

        {"id":"aee8a0de-c80f-4515-a232-501c0bc9d715", "type":"escalation"},

        {"name":"Nightwatch Escalation", "type":"escalation"},

        {"id":"80564037-1984-4f38-b98e-8a1f662df552", "type":"schedule"},

        {"name":"First Responders Schedule", "type":"schedule"}








    "actions": ["Restart", "AnExampleAction"],

    "tags": ["OverwriteQuietHours","Critical"],


    "entity":"An example entity",



I managed to figure out what the payload template in vROPs should look like.
This will give you a working payload template. I wasn't able to find any documentation on this. I ended up using Postman to look at an example of an existing Nagios alert and figured out that my format was wrong.

Remember to add the "$" in front of each parameter. I had to remove it here to be able to past the answer

"message": "{ALERT_DEFINITION}",
"details": {
                  "Alert Triggered On": "{RESOURCE_NAME}",
                  "Object Type:": "{RESOURCE_KIND}",
                  "Alert State": "{CONTROL_STATE}",
                  "Alert Priority": "{ALERT_CRITICALITY}",
                  "Object Impact": "{ALERT_SUBTYPE}",
                  "Object Symptoms": "{SYMPTOMS}"

Like Nick H likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events