Repository navigation
Add cluster UUID to the Logstash node datastream. - #9971
Conversation
|
I've started a stack and the logstash service defined in the _dev/deploy directory. after configuring the integration to collect metrics from the previously started logstash I can't see the |
Thanks @klacabane ! |
Map with a proper data shape. Co-authored-by: Rob Bavey <rob.bavey@elastic.co>
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
cc @mashhurs |
|
|
Package logstash - 2.4.7 containing this change is available at https://epr.elastic.co/search?package=logstash |





Proposed commit message
Logstash monitoring with metricbeat and self include
cluster_uuidwhich will be used during the queries (example telemetry collection). However, with agent driven monitoring we are losing the cluster UUID. This change fixes the explained bug.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Use the Logstash integration, install the agent and copy the change script into the policy. We can see the cluster UUID will be reflected in
.ds-metrics-logstash.node*indices. Also query againstcluster_uuid(which is an alias forlogstash.elasticsearch.cluster.id) also works as expected.Related issues
Screenshots