I can’t say that I’m too familiar with VictorOps, but I would assume that the workflow works something like this (based on supporting Synthetics/Alerts + similar notification systems like PagerDuty)
- Synthetics monitor fails
- Synthetics opens a violation (and an incident when applicable) in Alerts.
- When the incident opens, Alerts sends a notification to the service or notification channel (i.e. VictorOps, email, webhook, etc.)
That said, I suspect that this may actually be an issue with Alerts. If you can track down the incident that corresponds to this failure, it might reveal a bit more information. Specifically, it’ll allow you to see where and what notifications were sent, what timestamps were, and so on.
If you’re specifically looking to troubleshoot on the Synthetics side, you should be able to navigate to the specific failure to see more info. The extent to which verbose logs are available depends on the monitor, so there may be a limited amount of information that you can gather here with a ping monitor.
I’ll reiterate that I’m not overly familiar with VictorOps, but this should hopefully provide a bit more context with regards to how you could troubleshoot this. Any thoughts? Let me know!