Connect Synthetic Monitoring checks to your frontend applications
Connect Synthetic Monitoring checks to your frontend applications
You can now connect Synthetic Monitoring checks to the frontend applications they test. A check’s outside-in results then appear right next to that application’s health in the Knowledge graph. Frontend connections are available in public preview.
Frontend connections build on the Knowledge graph integration, which already connects checks to services. In the Labels step of the check editor, Knowledge Graph connections adds a Frontend application option next to Service, so you can connect a check to a frontend application, a service, or both. Choose a Frontend Observability application from the list, and Synthetic Monitoring stores its app ID on the check for you. When the Knowledge graph discovers the matching frontend, it links the application to your check. Insights from the check’s per-check alerts then count toward that application’s health.
Why it matters
A browser check that walks through a checkout touches both the frontend your users load and the backend services behind it. Connect the check to both, and the whole journey shows in one place. The Connected entities panel on the check’s dashboard shows the linked frontend and service, plus the service’s callers and dependencies, each with its own insights. When a check fails, you can see at a glance whether the frontend, a service, or something further downstream is also unhealthy. From there, open the full Entity graph or start a root cause analysis.
This works in the other direction too. The check’s health appears on the frontend application in the Knowledge graph, so the team that owns the app sees synthetic failures without having to look for the check.
Getting started
To use frontend connections, the Knowledge graph must be active on your stack and the application must be instrumented with Frontend Observability. To learn more, refer to Connect Synthetic Monitoring checks to the Knowledge graph.
