We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Elastic introduced rhe reroute processor with elastic/elasticsearch#76511 and it is available since 8.8.0.
I want to explore how to use the new Elasticsearch rerouting capabilities to support new use cases and bring more value to end users.
The text was updated successfully, but these errors were encountered:
Basic example of a pipeline that routes document based on Kubernetes labels:
--- description: Pipeline for Kubernetes container logs processors: - reroute: dataset: - '{{kubernetes.labels.elastic_co/dataset}}' - '{{data_stream.dataset}}' namespace: - '{{kubernetes.labels.elastic_co/namespace}}' - '{{data_stream.namespace}}'
The dataset and namespace can be a single value or and array. It will use the first valid value in the list.
dataset
namespace
Sorry, something went wrong.
zmoog
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
Elastic introduced rhe reroute processor with elastic/elasticsearch#76511 and it is available since 8.8.0.
I want to explore how to use the new Elasticsearch rerouting capabilities to support new use cases and bring more value to end users.
The text was updated successfully, but these errors were encountered: