Robert Paschedag
Robert Paschedag
@piotrp You are saying > - only the first of my three pipelines is visible in Kibana under correct cluster > - all of my three pipelines are visible under...
And if I read this correctly (https://github.com/elastic/logstash/blob/55e7a2641616b6c94e1390a6a921b54650ecd5a3/x-pack/lib/monitoring/inputs/metrics.rb#L227), when a `cluster_uuid` is found (because `elasticsearch.output` plugin is used, **that** is used. If `cluster_uuid` is missing and `monitoring.cluster_uuid` is set within the...
@piotrp Setting the `monitoring.cluster_uuid` within `logstash.yml` seems to fix the issue. I have tested this now in one example deployment in one of our clusters and the "missing" pipelines (ones...
So....at least seems partially fixed. I still see a lot of events within the `.monitoring-logstash-8-mb..` indices that do not have a `cluster_uuid` set an thus, are assigned to the standalone...
Sorry....some missing infos: - Stack Monitoring (elasticsearch, kibana, metricbeat): `8.4.1` version - logstash: latest code of `main` branch + PoC code
This screenshot was taken from the `.monitoring-logstash-8-mb` data-stream which has `dynmatic` set to `false` and no mapping for `cfs` fields exist
Change return types of "split" and "splitn" to map[string]interface{} (instead of map[string]string)
Sadly no. Only iterating via `range` and checking, if the key matches the desired string worked for me
Pretty sure, the Jenkins webhook job is stack and missing to push the results to github. An empty commit would already help to retrigger..
Anyone some interest?
Can confirm the issue still exists with version `2.8.0`. I was all time wondering, where my *custom* settings are gone, as I did not see them within the config files....