Quickstart: Create a Synthetic Monitor
Serverless
Elastic Synthetic monitoring is a comprehensive solution that allows organizations to proactively test and monitor applications by simulating user interactions, providing insights into performance metrics before real users encounter potential issues. This monitoring approach works by executing automated scripts that mimic typical user journeys and evaluating response times, error rates, and other critical performance indicators.
In this quickstart guide, you'll get more familiar with Elastic Observability as well as an overview on how to ingest, view, and get started with Synthetic monitoring.
-
Access your Elastic Cloud account
Go to cloud.elastic.co and access your account or create a new one.
-
Create a new project
Create a new Observability project. Make sure to select your preferred cloud region when you create your first project. Refer to Create an Observability project for more details.
-
Go to Synthetics
Once your deployment is complete click Applications and select Monitors under Synthetics.
There are two ways to run synthetic monitors which will depend on if the website or app being tested are accessible from:
- Elastic's global managed testing infrastructure: With Elastic's global managed testing infrastructure, you can create and run monitors in multiple locations without having to manage your own infrastructure. Elastic takes care of software updates and capacity planning for you. This is perfect for testing websites or applications that are accessible from the public internet.
- Private networks support allows you to run monitors from your own premises. To run monitors from your own private network you must create a Private Location before continuing. For step-by-step instructions, refer to Monitor resources on private networks.
This guide shows how to leverage Elastic's global managed testing infrastructure.
NoteProjects let you define your infrastructure as code. With project monitors you organize your YAML configuration and JavaScript- or TypeScript-defined monitors on the filesystem, use Git for version control, and deploy via a CLI tool, usually executed on a CI/CD platform. Refer to Create monitors with project monitors.
-
Create a browser monitor
Create a single page browser monitor. Make sure to select a URL and the locations where monitors will be executed, then select Create monitor.
Synthetics will be executing the test across all of those locations, automatically refreshing the screen.
-
Turn on alerts
If there are any issues, you might want to turn on alerts:
- Select Configure now from the Alerts warning, or go to Settings and then Alerting.
- Select the default connector, which is already prepopulated when you deploy Elastic. After you select your default connector you can add your default email address to receive the alerts.
- Go back to Monitors, select Alerts and rules then Monitor status rule. A dialog will appear where you can edit your alerts. You can also select alternate connector types, such as Slack, Microsoft Teams, and more.
When you set up alerts and receive notifications, you’ll also receive a deep link directly into the Error details page. From here you can see:
- What step failed
- Screenshot of the failed step
- Screenshot of the last time that step was successful
- The times of the failed step and last time step was successful to compare
- What code was executed
- What the browser is showing
-
Analyze your monitor data
Go to Monitors and select one of the monitors, you’ll see a dialog with a quick summary of the monitor. Select Go to monitor to see high level insights. Charts will start to render as more tests come through but you can quickly see the availability, the duration to execute tests, the timeline, and you can also drill down into the waterfall chart.
To drill down, select the icon under View test run. From here you can see the waterfall chart, object weight, object count, and more.