You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the feature request.
Elasticsearch has support for 2 types of templates, an index template (what the ElasticMeterRegistry is using) and Component Templates. Component templates allow you to create an index template consisted of multiple different components.
Rationale
The reason for this change request is the fact that we would like to apply a lifecycle policy for the metrics template. The way to achieve this is by using an index template that looks like:
However, this would fail as there is already a registered metrics template from Micrometer called metrics_template.
We could circumvent this failure, by adding a priority, but then the template with the highest priority would take precedence, and this is not what we want, we want to combine the both index templates.
One way would be to copy the Micrometer template, but then we need to keep maintaining that with every Micrometer release.
If Micrometer registers a component template then we can use a template that looks like:
Please describe the feature request.
Elasticsearch has support for 2 types of templates, an index template (what the
ElasticMeterRegistry
is using) and Component Templates. Component templates allow you to create an index template consisted of multiple different components.Rationale
The reason for this change request is the fact that we would like to apply a lifecycle policy for the metrics template. The way to achieve this is by using an index template that looks like:
However, this would fail as there is already a registered metrics template from Micrometer called
metrics_template
.We could circumvent this failure, by adding a priority, but then the template with the highest priority would take precedence, and this is not what we want, we want to combine the both index templates.
One way would be to copy the Micrometer template, but then we need to keep maintaining that with every Micrometer release.
If Micrometer registers a component template then we can use a template that looks like:
With this approach, when Micrometer changes the template we don't need to do anything, it will just be applied automatically on all the new indices.
The text was updated successfully, but these errors were encountered: