-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Migrate ops metrics to New Platform #46563
Comments
Pinging @elastic/kibana-platform |
This is the exact data we need from a combination of
|
@chrisronline On which extends the data structure must remains exactly the same as what we had before? I would really like to take this NP migration as an opportunity to cleanup / restructure the raw output format a little bit. More specifically, I was thinking on merging the Would that be acceptable to you / would you be able to convert back to the stats endpoint expected format, or would that be really bothersome to you? Note that we will now have TS typings to back us up, so this would be easier to convert than the current untyped TS implementation. |
I don't have a strong opinion either way I guess, but if we're changing the structure within the monitoring document itself, that would be a breaking change and we'd have to wait for a major to do that. We should probably keep it consistent for now, and work on changing the structure for 8.0. WDYT? |
I'll keep it that way in #58623 for now then |
Being consumed by legacy platform and monitoring plugin. Move to a separate NP plugin or to the core service
The text was updated successfully, but these errors were encountered: