Comments
-
were you able to get this resolved?
-
Thanks, I completely forgot about monitoring the log file. For reference this is the file where logs are kept when alerts fail: C:\ProgramData\SolarWinds\Logs\Orion\ActionsExecutionAlert.log I'm not certain on how to capture it within SAM or via the servers capabilities, but this puts me in the right direction. When I get…
-
I'm in favor of this as well. It's roundabout, but at least I can deal with one common json format and send it out to the different parties, rather than trying to mess with someone else's json to make it work for us.
-
Is there away to retireve the http response from pagerduty? I want to be able to log an error somewhere if the pagerduty events v2 api wasn't able to ingest the http POST from solarwinds.