Skip to content
New issue

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

[8.0] Kibana GET /api/stats breaking changes #27569

Open
afharo opened this issue Aug 24, 2021 · 3 comments
Open

[8.0] Kibana GET /api/stats breaking changes #27569

afharo opened this issue Aug 24, 2021 · 3 comments

Comments

@afharo
Copy link
Member

afharo commented Aug 24, 2021

Describe the enhancement:
Kibana is planning to remove the process info structure from its metrics (elastic/kibana#104124). This will likely affect Metricbeat's Kibana stats and status modules.

Describe a specific use case for the enhancement or feature:
The reasoning for removing that piece of info from the responses is detailed in the issue: elastic/kibana#104124.

TL;DR: For 8.0, we are planning on adding support to Kibana running multiple sub-processes in the same host. This means that process is unlikely to be meaningful anymore.

Related PRs:

@elasticmachine
Copy link
Collaborator

Pinging @elastic/stack-monitoring (Stack monitoring)

@matschaffer
Copy link
Contributor

@sayden here's the json I was looking at testing for changes to https://github.com/elastic/beats/blob/master/metricbeat/module/kibana/stats/stats.go

7-15-1.json.zip
multi-process.json.zip

My thinking is that beats 8 could "upgrade" kibana <=7 from process: {} to processes: [{},...] and store that way.

Then in elastic/kibana#113149 I'll see if I can do the same thing via runtime fields so that the UI can plot old data in the new format and switch current graphs to be multi-line.

Given the title of this issue maybe we should check for /api/status changes as well. I haven't yet. Or maybe @mshustov or @Bamieh can confirm if anything on that API is changing as well.

@matschaffer
Copy link
Contributor

Looks like all beats reads from /api/status is version.number anyway which doesn't appear to have changed between 7.15.1 and master. I'll update the title of this ticket. Feel free to change back if someone finds otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants