-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Component/s: Integrations - 3rd-party - Azure
-
None
-
1
-
Severity 2 - Major
Issue Summary
The integration between Microsoft Azure Resource Health and Opsgenie is not working out-of-box.
As per Microsoft's documentation, monitoringService = Resource Health and Opsgenie integration documentation Integrate with Microsoft Azure Resource Health, the payload from Azure includes two status fields:
- data.status which returns "Activated" parsed as status
- data.context.activityLog.status which returns "Active" - Parsed as activitLogStatus
For data.context.activityLog.status, Opsgenie expects a value of "Started" by default. This can be customized for Enterprise plans but not for Essentials.
Steps to Reproduce
- Setup an integration between Opsgenie and Microsoft Azure Resource Health following Integrate with Microsoft Azure Resource Health
- Send a log alert from Azure
Expected Results
The value "Active" is accepted, the request is processed, and an alert is created in Opsgenie
Actual Results
The processing fails, and no alerts are created
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available.