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
When running in x-pack mode, it is expected that all data from the Elasticsearch module should land in the .monitoring-* data stream, but the ingest_pipeline metricset doesn't override the target data stream before the events are shipped, leading them to land in metricbeat-*.
Fixing this issue in the Beats code is trivial, but it will also require us to update the Elasticsearch Ingest Pipeline dashboard found in the Elasticsearch integration.
The text was updated successfully, but these errors were encountered:
When running in x-pack mode, it is expected that all data from the Elasticsearch module should land in the
.monitoring-*
data stream, but theingest_pipeline
metricset doesn't override the target data stream before the events are shipped, leading them to land inmetricbeat-*
.Fixing this issue in the Beats code is trivial, but it will also require us to update the Elasticsearch Ingest Pipeline dashboard found in the Elasticsearch integration.
The text was updated successfully, but these errors were encountered: