-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Add the cluster_uuid field to Enterprise search stats metricset #28287
Add the cluster_uuid field to Enterprise search stats metricset #28287
Conversation
…ke it easier to correlate with health metricset events
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
Integration tests will keep failing until we have a 7.16-SNAPSHOT build of enterprise search with the changes I've made today. |
/test |
Pinging @elastic/integrations (Team:Integrations) |
@@ -31086,7 +31086,7 @@ type: keyword | |||
-- | |||
|
|||
[[exported-fields-enterprisesearch]] | |||
== enterprisesearch fields | |||
== Enterprise Search fields |
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.
Just noticed we can control this via our module metadata and decided to make it prettier
[float] | ||
=== product_usage | ||
|
||
Aggregate product usage statistics for the Enterprise Search deployment. |
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.
Added a few more fields from our stats endpoint to improve the Stack Monitoring experience
@@ -3,10 +3,6 @@ | |||
release: beta | |||
description: Enterprise Search health | |||
fields: | |||
- name: cluster_uuid |
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.
Moved this to the module level
Thoroughly tested this while developing the Stack Monitoring integration and it works really well. |
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.
Good! Moving UUID to top level makes sense, and the additional fields are great for monitoring 👍
This PR is blocking the testing Kibana team needs to do on the Stack Monitoring integration PR: elastic/kibana#114303 (comment). If we could get this reviewed sooner rather than later, it'd be hugely appreciated 🙇🏻 |
@masci Can you chime in on who should give a 👍 from your team? |
@richkuz I'm ok merging this even without reviews from my team, @carlosdelest already approved and you folks know better than us. Feel free to fully own this module, should you have any issue/doubt we'll be happy to help but other than that, no need to include us in the development process. Thanks for adding more features to the solution! |
* Add the cluster_uuid field to Enterprise search stats metricset to make it easier to correlate with health metricset events * Make Enterprise Search module field docs prettier * Updated the docs * Move cluster_uuid to the module level to make it easier to filter those events in Stack monitoring * Add product usage metrics to the stats event * Update mb docs following the addition of new fields * Remove duplicate uuid fields now that we put the uuid at the module level (cherry picked from commit 78bcab3) # Conflicts: # metricbeat/docs/fields.asciidoc
…h stats metricset (#28505) * Add the cluster_uuid field to Enterprise search stats metricset (#28287) * Add the cluster_uuid field to Enterprise search stats metricset to make it easier to correlate with health metricset events * Make Enterprise Search module field docs prettier * Updated the docs * Move cluster_uuid to the module level to make it easier to filter those events in Stack monitoring * Add product usage metrics to the stats event * Update mb docs following the addition of new fields * Remove duplicate uuid fields now that we put the uuid at the module level (cherry picked from commit 78bcab3) # Conflicts: # metricbeat/docs/fields.asciidoc * Fix the conflict Co-authored-by: Oleksiy Kovyrin <oleksiy@kovyrin.net>
…tic#28287) * Add the cluster_uuid field to Enterprise search stats metricset to make it easier to correlate with health metricset events * Make Enterprise Search module field docs prettier * Updated the docs * Move cluster_uuid to the module level to make it easier to filter those events in Stack monitoring * Add product usage metrics to the stats event * Update mb docs following the addition of new fields * Remove duplicate uuid fields now that we put the uuid at the module level
What does this PR do?
This PR adds the
cluster_uuid
field to Enterprise search stats metricset to make it easier to correlate with health metricset events. Additionally, in both metricsets, we have moved the cluster_uuid field to the module level to make it easier to aggregate data across two event types in Stack monitoring and Kibana dashboards.Why is it important?
This is a follow-up for the recent PR that added the new module and we have just realized that having a uuid in all of our fields would make correlating them in Kibana a lot easier and make those events easier to work with in Kibana monitoring plugin (that relies on cluster UUID to group stack components together).
Checklist
I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
metricbeat
with theenterprisesearch
module enabledstats
events produced by theenterprisesearch
module and you'll see the new field.Alternatively, one can use integration tests to make sure the changes work (I've added data tests changes needed).
Related issues