search

elastic / beats

:tropical_fish: Beats - Lightweight shippers for Elasticsearch & Logstash
https://www.elastic.co/products/beats
Other
12.08k stars 4.89k forks source link

[Metricbeat] Kibana module is not compatible with Kibana 8.x when in xpack mode #32695

Open weltenwort opened 1 year ago

weltenwort commented 1 year ago

:lady_beetle: Bug report

:1234: Steps to reproduce

  1. Set up a cluster of the newest 8.x release with Kibana.
  2. Download or build metricbeat version 7.17.5.
  3. Enable the kibana metricbeat module and configure it to connect to the cluster's Kibana instance.
  4. Start metricbeat.
  5. Observe that metricbeat logs a 404 when trying to access the route /api/settings of the Kibana instance.

:thought_balloon: Context

The route /api/settings was removed in 8.0.0 on the Kibana side. On the metricbeat the kibana module was refactored to extract the code calling that API into the settings metricset. For 7.17, though the call to the settings API is still part of the stats metricset and results in a 404. Although it is guarded by a version check, that check only guards against version < 6.4, but not > 8.0.

It seems that https://github.com/elastic/beats/issues/21119 was supposed to fix this, but was closed without a clean resolution.

matschaffer commented 1 year ago

Is there a functional failure as well, or just 404 log noise?

weltenwort commented 1 year ago

I'm not very fluent in golang, but the call to the missing /api/settings route seems to be the last step in the polling cycle. The documents that correspond to the stats and status API calls seem to be emitted beforehand. I don't know enough to judge whether there's something else in the beat framework that is negatively impacted by these errors. Maybe a more qualified beats dev can give their opinion.

elasticmachine commented 1 year ago

Pinging @elastic/integrations (Team:Integrations)

botelastic[bot] commented 11 months ago

Hi! We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!