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

[5.x][status api] opt in to v6 metrics #10481

Merged
merged 4 commits into from
Feb 27, 2017
Merged

Conversation

jbudz
Copy link
Member

@jbudz jbudz commented Feb 21, 2017

This is an opt-in backport of #10180, returning only the latest metrics from the status api. It can be enabled by setting status.v6ApiFormat: true in kibana.yml

metrics: kbnServer.v6Metrics
});
}

return reply({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This return should be legacy format with without the nested version information. Metrics also needs to be of the legacy format.

kbnServer.metrics = new Samples(12);

server.plugins['even-better'].monitor.on('ops', function (event) {
kbnServer.v6Metrics = getV6Metrics({ event, config });
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What are your thoughts on swapping this, creating kbnServer.legacyMetrics. Reason being is we are exposing the cgroup information via this interface.

@@ -148,7 +148,8 @@ module.exports = () => Joi.object({
}).default(),

status: Joi.object({
allowAnonymous: Joi.boolean().default(false)
allowAnonymous: Joi.boolean().default(false),
v6Api: Joi.boolean().default(true)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should default this to false.

@jbudz
Copy link
Member Author

jbudz commented Feb 27, 2017

jenkins, test this

Copy link
Contributor

@tylersmalley tylersmalley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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

Successfully merging this pull request may close these issues.

2 participants