Summary: The Entities API endpoint /api/v2/entities and Grail return a property 'isEnabled' for each Synthetic Monitor. This status is reflected in the Dynatrace Synthetic app in the latest Dynatrace. For some monitors, this value does not match what is seen in the Classic Synthetic app or what is returned by /api/v1/synthetic/monitors
Problem
There was a bug in setting the correct value for the property 'isEnabled' for Synthetic Monitors. This affects the /api/v2/entities endpoint, Grail, and the latest Synthetic app. The Classic Synthetic app and /api/v1/synthetic/monitors show the correct value.
The bug was fixed in Cluster 1.298. The configuration of synthetic monitors is correct, and they're being executed as expected. However, any monitors affected by this behavior need manual intervention to correct the values returned in the latest Synthetic app, Grail and the /api/v2/entities endpoint.
Resolution
For any Synthetic Monitors showing this behavior
- Toggle the monitor status, ie, enable and then disable the monitor if it's disabled, or disable and then enable the monitor if it's enabled.
What's next
If none of the previous steps resolved the issue, then open a chat and provide a link to the affected monitor and mention this article.
Synthetic Troubleshooting Map
Synthetic app