Details
-
Suggestion
-
Resolution: Unresolved
-
None
Description
User Problem
In the current design, when an alert is ack'ed in Opsgenie using the respective action, OEC takes the value held in the "login" parameter from the config.json file under OEC folder. If this value is "admin", all the alerts will have that value for the "Acknowledged By" field:
Suggested Solutions
The OEC script includes a "comment" as part of the payload sent to Solarwinds. This comment contains more details about the action that was performed.
In addition to the above, the output.txt file also logs a "warning" record when an alert is acknowledged which includes the following text:
Current Workarounds
This is not considered a workaround but an observed behavior.
The Opsgenie alert details include a field named "Acknowledge URL" which is a direct link from Solarwinds to ack the alert there. If a user clicks on that link, the alert will be acknowledged directly in Solarwinds and the "Acknowledged By" field will take the info of the user who performed the action. However, Solarwinds doesn't inform Opsgenie back about this action causing the user to also have to "ack" the alert on Opsgenie's end.