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
Next: Root
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.
Hi,
I am trying trying to create an alert in opsgenie using Logz.io integration
https://api.eu.opsgenie.com/v1/json/logzio?apiKey=XXXX
and JSON:
{ "alert_title": "my new alert", "alert_description": "new alert description", "alias": "my alert alias"}
The alert is created fine but not with the specified alias. Why is this?
Hi @myron lioz !
I think the main issue here is the payload for two different "integrations" are being combined.
For 3rd party integrations like logz.io, Opsgenie does not control the payload format being used. While you can "mock" a specific request using the integration's field (as you did in your post), the way those fields translate onto the alert is mostly determined by the integration settings:
So if you want to use this method to set an alias in the logz.io integration, what you'd really need to do is set the fields that make up the alert alias according to the integration settings in Opsgenie. That is, make sure the alias is set in the integration settings, then set the fields that make up the alias in the payload to Opsgenie.
Does that help clarify why the request you sent wasn't setting the alias?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.