- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.8
- Get started
- Application performance monitoring (APM)
- Logs
- Infrastructure monitoring
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- Synthetics support matrix
- Synthetics Encryption and Security
- Uptime monitoring
- Real user monitoring
- Universal Profiling (beta)
- Alerting
- Service-level objectives (SLOs) (beta)
- Cases
- CI/CD observability
- Troubleshooting
- Fields reference
- Tutorials
- Monitor Amazon Web Services (AWS) with Elastic Agent
- Monitor Amazon Web Services (AWS) with Beats
- Monitor Google Cloud Platform
- Monitor a Java application
- Monitor Kubernetes
- Monitor Microsoft Azure with Elastic Agent
- Monitor Microsoft Azure with the Azure Native ISV Service
- Monitor Microsoft Azure with Beats
Manage data retention
editManage data retention
editWhen you set up a synthetic monitor, data from the monitor is saved in Elasticsearch data streams, an append-only structure in Elasticsearch.
There are six data streams recorded by synthetic monitors: http, tcp, icmp, browser, browser.network, browser.screenshot.
Elastic will retain data from each data stream for some time period,
and the default time period varies by data stream.
If you want to reduce the amount of storage required or store data for longer,
you can customize how long to retain data for each data stream.
Synthetics data streams
editThere are six data streams recorded by synthetic monitors:
| Data stream | Data includes | Default retention period | |
|---|---|---|---|
|
The URL that was checked, the status of the check, and any errors that occurred |
1 year |
|
|
The URL that was checked, the status of the check, and any errors that occurred |
1 year |
|
|
The URL that was checked, the status of the check, and any errors that occurred |
1 year |
|
|
The URL that was checked, the status of the check, and any errors that occurred |
1 year |
|
|
Binary image data used to construct a screenshot and metadata with information related to de-duplicating this data |
14 days |
|
|
Detailed metadata around requests for resources required by the pages being checked |
14 days |
All types of checks record core metadata. Browser-based checks store two additional types of data: network and screenshot documents. These browser-specific indices are usually many times larger than the core metadata. The relative sizes of each vary depending on the sites being checked with network data usually being the larger of the two by a significant factor.
Customize data stream lifecycles
editIf Synthetics browser data streams are storing data longer than necessary, you can opt to retain data for a shorter period.
To find Synthetics data streams:
- Navigate to Kibana index management.
-
Filter the list of data streams for those containing the term
synthetics.-
In the UI there will be three types of browser data streams:
synthetics-browser-*,synthetics-browser.network-*, andsynthetics-browser.screenshot-*.
-
In the UI there will be three types of browser data streams:
Then, you can refer to Tutorial: Customize data retention for integrations to learn how to apply a custom ILM policy to the browser data streams.