-
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
CI Reporter for saved objects field count #70580
Conversation
3d78ad8
to
e09c77b
Compare
Pinging @elastic/kibana-platform (Team:Platform) |
@elasticmachine merge upstream |
This reverts commit 8c0126b.
Would be really cool if we could attribute unique fields to a specific plugin and shared fields separately... |
Yeah, as a first step we could track unique fields per type which would allow us to infer the plugin that added these. |
|
||
await Promise.all( | ||
fieldCountPerType | ||
.sort((a, b) => a[0].localeCompare(b[0])) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We also sort things server-side
@elasticmachine merge upstream |
💚 Build SucceededBuild metricsSaved Objects .kibana field count
History
To update your PR or re-run it, just comment with: |
* CI Reporter for saved objects field count * Metrics needs to be an array * Fix type failures * Link to field count issue * Revert "Link to field count issue" This reverts commit 8c0126b. * Break down field count per type * Don't log total metric as metrics report already calculates this * Add saved objects field count ci metrics test to codeowners * Address review comments * Add field count CI metrics for disabled plugins Co-authored-by: Elastic Machine <[email protected]> # Conflicts: # .github/CODEOWNERS
* CI Reporter for saved objects field count (#70580) * CI Reporter for saved objects field count * Metrics needs to be an array * Fix type failures * Link to field count issue * Revert "Link to field count issue" This reverts commit 8c0126b. * Break down field count per type * Don't log total metric as metrics report already calculates this * Add saved objects field count ci metrics test to codeowners * Address review comments * Add field count CI metrics for disabled plugins Co-authored-by: Elastic Machine <[email protected]> # Conflicts: # .github/CODEOWNERS * Don't backport CODEOWNERS file to 7.x
Summary
Introduces CI metrics for Saved Object field count broken down by Saved Object type. This will help teams review the impact their PR has on the field count and allow us to track this metric over time.
Known limitations:
enabled
config to default tofalse
. Fields contributed by these plugins won't show up in these metrics. We will need a way to start Kibana with all discovered plugins enabled which would either require moving this to a jest_integration test usingtest_utils
and internal API's or exposing a command line flag.migrationVersion
field count #70815 Can introduce an additional ~114 fields and if users have upgraded from older versions of Kibana they can have additional fields on their.kibana
that's not present when testing a clean index Saved Object Migrations should clean up unused mappings #67086.Checklist
For maintainers