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 project monitors, you should also set up a workflow that uses best practices for managing monitors effectively in a production environment.
Update a monitoredit
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 projects,
you’ll update the monitor in the project source and then
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
- To update the configuration of all monitors in a project, edit the global synthetics configuration file.
To update the journey 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
to replace the existing monitors in Kibana 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.
If you set up the monitor using the Synthetics app, you can update the monitor configuration of both lightweight and browser monitors in the Synthetics app:
- Go to Management.
- Click the pencil icon next to the monitor you want to edit.
Update the Monitor settings as needed.
- To update the journey used in a browser monitor, edit Inline script.
- Make sure to click Run test to validate the new journey before updating the monitor.
- Click Update monitor.
Delete a monitoredit
Eventually you might want to delete a monitor altogether. For example, if the user journey you were validating no longer exists.
If you set up the monitor using projects, you’ll delete the monitor from the project source and push changes.
For lightweight monitors, delete the monitor from the YAML file.
Then, run the
The monitor associated with that journey that existed in Kibana will be deleted.
If you set up the monitor using the Synthetics app, you can delete a lightweight or browser monitor in the Synthetics app:
- Go to Management.
- Click the trash can icon next to the monitor you want to delete.
Alternatively, you can temporarily disable a monitor by updating the monitor’s configuration in your journey’s code or in the Synthetics app using the Enabled toggle.
Implement best practices for projectsedit
This is only relevant to monitors created using projects.
After you’ve set up a project, there are some best practices you can implement to manage project monitors effectively.
Use version controledit
First, it’s recommended that you version control all files in Git. If your project is not already in a version controlled directory add it and push it to your Git host.
Set up recommended workflowedit
While it can be convenient to run the
push command directly from your workstation,
especially when setting up a new 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 pushafter 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
directory when you create a new project.