-
Notifications
You must be signed in to change notification settings - Fork 25.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new index for synthetics #61665
Comments
Pinging @elastic/es-core-features (:Core/Features/Features) |
@andrewvc as I understand it, we only need a template (similar to our |
I would suggest we use the same templates we have for logs / metrics at the moment for synthetics. The detailed data_stream templates will be set up Uptime before data is shipped but having the template in Elasticsearch ensures nobody messed with the indices/data streams in advance. |
A PR to get it into ES :-) |
@dakrone I take it you're the one to open the PR? |
@andrewvc I have been on vacation for the past 11 days, but yes, either me or someone on the core/features team would likely work on this |
These two templates have slightly different mappings (logs have a "message" field), should the |
For the Elastic Agent we currently have `logs` and `metrics`, however, synthetic data doesn't belong with those and thus we should have a place for it to live. This would be data reported from heartbeat and under the 'monitoring' category. This commit adds a composable index template for `synthetics-*-*` indices similar to the work in elastic#56709 and elastic#57629. Resolves elastic#61665
My guess is that we don't need the |
* Add "synthetics-*-*" templates for synthetics fleet data For the Elastic Agent we currently have `logs` and `metrics`, however, synthetic data doesn't belong with those and thus we should have a place for it to live. This would be data reported from heartbeat and under the 'monitoring' category. This commit adds a composable index template for `synthetics-*-*` indices similar to the work in #56709 and #57629. Resolves #61665
* Add "synthetics-*-*" templates for synthetics fleet data For the Elastic Agent we currently have `logs` and `metrics`, however, synthetic data doesn't belong with those and thus we should have a place for it to live. This would be data reported from heartbeat and under the 'monitoring' category. This commit adds a composable index template for `synthetics-*-*` indices similar to the work in elastic#56709 and elastic#57629. Resolves elastic#61665
… (#62346) * Add "synthetics-*-*" templates for synthetics fleet data For the Elastic Agent we currently have `logs` and `metrics`, however, synthetic data doesn't belong with those and thus we should have a place for it to live. This would be data reported from heartbeat and under the 'monitoring' category. This commit adds a composable index template for `synthetics-*-*` indices similar to the work in #56709 and #57629. Resolves #61665
For the new Elastic agent, there are two current index types are logs and metrics. Synthetics doesn't really fit with that, we should add a new synthetics index for data reported from heartbeat. This would be under the 'monitoring' category.
A question I have is about the fields that should be included in ES. We don't really have a 'minimal' subset. We need all our fields for the Uptime UI to be rendered correctly. Should we include all our field mappings with the index in ES?
CC @ruflin @ph
The text was updated successfully, but these errors were encountered: