This functionality is in beta and is subject to change. The design and code is less mature than official GA features and is being provided as-is with no warranties. Beta features are not subject to the support SLA of official GA features.
After you’ve created a synthetic monitor, you can update the contents of the tests that they run, update the monitor’s configuration, and permanently delete monitors.
The way you manage browser monitors will depend on how you created the monitor:
Update a journeyedit
After you create a monitor, you might want to update the journey it runs. If you update your UI, for example, you may want to update your journey’s selectors and assertions.
Update the tests in the directory specified in the
source.zip_url you referenced in the Heartbeat configuration file, and the changes will be reflected in the monitors.
If you’re using inline monitors within your
heartbeat.yml configuration file, update your monitors directly in that file.
If you’re using project monitors, you can update journeys directly through code.
Then run the
push command to replace any existing monitors from this project in Kibana with new monitors that use the updated test.
Updates are linked to a monitor’s
id. To update a monitor you must keep its
id the same.
Update the tests at the Zip URL you referenced in the Elastic Agent Integration when you configured the monitor, and the changes will be reflected in the monitors.
Update a monitor’s configurationedit
You might also want to update the monitor’s configuration. For example, you might want to change the interval at which the monitor runs a test.
Update the relevant options in the Heartbeat configuration file, and the changes will be reflected in the monitors.
Update the monitor configuration options used in individual journeys in the test code (or in the
global synthetics configuration file).
Then run the
push command to replace the existing monitor in Kibana with a new monitor that uses the updated configuration options.
After creating an integration you can edit the configuration. Any changes you make will be applied to all agents to which the policy (that contains an integration) applies.
Delete a synthetic monitoredit
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.
To remove a monitor using Heartbeat, delete the monitor entry in the
Delete the journey in the test code and push the project using the
The monitor associated with that journey that existed in Kibana will be deleted.
To remove a monitor that you created using Elastic Agent, delete the integration.