01 Feb 2024 11:03 AM - edited 15 Sep 2025 03:23 PM
When troubleshooting intermittent HTTP Monitor failures, it can be helpful to know which ActiveGate, within a location, the execution ran on.
HTTP monitor executions show the synthetic location that they were run on in the execution details, along with the engineId. This article shows how to find this information and then the ActiveGate that the engineId refers to.
Note: these steps are only for Private Locations, not Cluster or Public locations
If you weren't able to find the ActiveGate that ran the execution using the steps above, open a chat and a link to the execution you are interested. This is the same for Cluster and Public locations.
You can find further troubleshooting tips for Synthetic in the Synthetic Troubleshooting Map