Manage monitors

[preview] This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.

After you’ve created a synthetic monitor, you’ll need to manage that monitor over time. This might include updating or permanently deleting an existing monitor.

If you’re using a Synthetics project to manage monitors, you should also set up a workflow that uses best practices for managing monitors effectively in a production environment.

Update a monitor

edit

You can update a monitor’s configuration, for example, changing the interval at which the monitor runs a test.

You can also update the journey used in a browser monitor. For example, if you update the UI used in your application, you may want to update your journey’s selectors and assertions.

If you set up the monitor using a Synthetics project, you’ll update the monitor in the Synthetics project and then push changes to your Observability project.

For lightweight monitors, make changes to the YAML file.

For browser monitors, you can update the configuration of one or more monitors:

To update the configuration of an individual monitor, edit the journey directly in the JavaScript or TypeScript files, specifically the options in monitor.use.
To update the configuration of all monitors in a Synthetics project, edit the global synthetics configuration file.

To update the journey that a browser monitor runs, edit the journey code directly and test the updated journey locally to make sure it’s valid.

After making changes to the monitors, run the push command to replace the existing monitors with new monitors using the updated configuration or journey code.

Updates are linked to a monitor’s id. To update a monitor you must keep its id the same.

Delete a monitor

edit

Eventually you might want to delete a monitor altogether. For example, if the user journey you were validating no longer exists.

Alternatively, you can temporarily disable a monitor by updating the monitor’s configuration in your journey’s code or in the Synthetics UI using the Enabled toggle.

Implement best practices for Synthetics projects

edit

This is only relevant to monitors created using a Synthetics project.

After you’ve set up a Synthetics project, there are some best practices you can implement to manage the Synthetics project effectively.

Use version control

edit

First, it’s recommended that you version control all files in Git. If your Synthetics project is not already in a version controlled directory add it and push it to your Git host.

Set up recommended workflow

edit

While it can be convenient to run the push command directly from your workstation, especially when setting up a new Synthetics project, it is not recommended for production environments.

Instead, we recommended that you:

Develop and test changes locally.
Create a pull request for all config changes.
Have your CI service automatically verify the PR by running npx @elastic/synthetics .

Elastic’s synthetics runner can output results in a few different formats, including JSON and JUnit (the standard format supported by most CI platforms).

If any of your journeys fail, it will yield a non-zero exit code, which most CI systems pick up as a failure by default.
Have a human approve the pull request.
Merge the pull request.
Have your CI service automatically deploy the change by running npx @elastic/synthetics push after changes are merged.

The exact implementation details will depend on the CI system and Git host you use. You can reference the sample GitHub configuration file that is included in the .github directory when you create a new Synthetics project.

« Configure lightweight monitors Work with params and secrets »