-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"extraProperties" or "Details (Key-Value Based)" on alert create #51
Comments
What sort of extra properties would you want to be adding to the alert creation request? |
the "extraProperties" noted here https://docs.opsgenie.com/docs/integration-api. Within Opsgenie integrations and policies, these are also known as "Details (Key-Value Based)", and can be used to help filter/chain alerts. screenshots are from a slack integration's "Alert Filter:" |
"extraProperties" must be deprecated, I think they now use "details" in its place. Command line curl direct to Opsgenie's REST API, I am sending "details" as JSON, and it is converted to "_extraProperties" within the Opsgenie logs. "details" is referenced here: https://docs.opsgenie.com/docs/alert-api You definitely want to consider adding "details" to the sensu-opsgenie API, it is extremely useful. |
If I manually add the field by selecting from dropdown "Details(Key-Value Based)", I am able to add to opsgenie.
But then if I want to push same value (POST method) through code by adding above object, I am not able to. :( Can someone help me with this? |
I got the answer! It's working While posting data in Opsgenie, for a Key-Value based entity, |
Maybe it's staring me in the face, but is there a way to add "extraProperties" during alert create? I know "tags" exist, but they can get messy quick.
The text was updated successfully, but these errors were encountered: