You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When using the default SolarWinds Orion NPM integration, variables are parsed directly.
But when using a powershell rest api as alert action in SolarWinds then API integration in OpsGenie, the variables from SolarWinds are not parsed.
Good observation. Comparing the two integrations's blue draggable fields on the right of their Advanced integration view, most of the field names are different between the two integrations.
The SolarWinds Orion NPM integration was built for that specific payload; whereas the API Integration in Opsgenie uses the Alert API endpoint for alert creation and it expects a payload that is likely quite different from the one sent by the powershell rest api.
If you capture that payload using a tool like beeceptor.com, you may be able to extract the values of the fields you want by using dynamic fields, string processing, and/or regular expressions.
Please feel free to contact us at Customer Support for additional assistance!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.