-
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
[Metricbeat] Enterprise Search Module #27549
[Metricbeat] Enterprise Search Module #27549
Conversation
💚 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:
|
…ure for mage binaries
…c module when running with mage against x-pack metricbeat directory
…e master now. This reverts commit 5bf6fb2.
…prise-search-metricbeat-module
…ced this on M1, but not sure if it is M1-specific)
…prise-search-metricbeat-module
…sing documentation error messages are produced in a predictable and repeatable order. This is really helpful when someone is trying to fix multiple issues and wants to make sure a specific issue is fixed before moving one to the next one. Otherwise, the errors are thrown in a random order and every time a new message is presented to the developer making it very confusing if the previous one had been resolved or not.
…prise-search-metricbeat-module
Ok, all of those changes unrelated to this PR have been merged, so now the diff should only contain the new module |
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.
Thank you for the field rework. I leave you the "honor" of merging 🙂
@mergify backport |
Added Enterprise Search module with two metricsets: health and stats, each using a corresponding API endpoint Co-authored-by: Oleksiy Kovyrin <oleksiy@kovyrin.net> (cherry picked from commit 3c77c9a) # Conflicts: # metricbeat/docs/fields.asciidoc
Command
Hey, I reacted but my real name is @Mergifyio |
Added Enterprise Search module with two metricsets: health and stats, each using a corresponding API endpoint Co-authored-by: Oleksiy Kovyrin <oleksiy@kovyrin.net>
* [Metricbeat] Enterprise Search Module (#27549) Added Enterprise Search module with two metricsets: health and stats, each using a corresponding API endpoint Co-authored-by: Oleksiy Kovyrin <oleksiy@kovyrin.net> (cherry picked from commit 3c77c9a) # Conflicts: # metricbeat/docs/fields.asciidoc * [Metricbeat] Enterprise Search Module (#27549) Added Enterprise Search module with two metricsets: health and stats, each using a corresponding API endpoint Co-authored-by: Oleksiy Kovyrin <oleksiy@kovyrin.net> * Fix the issue with the linux module not being loaded on a mac Co-authored-by: Carlos Delgado <6339205+carlosdelest@users.noreply.github.com> Co-authored-by: Oleksiy Kovyrin <oleksiy@kovyrin.net> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Added Enterprise Search module with two metricsets: health and stats, each using a corresponding API endpoint Co-authored-by: Oleksiy Kovyrin <oleksiy@kovyrin.net>
Originally, a Space Time ON project from @carlosdelest, later adopted into the roadmap and developed by @kovyrin.
What does this PR do?
Created a new Enterprise Search module, based on current App Search module. Created the first MetricSet that uses the Health API to get metrics. We're planning to add a couple more metricsets going forward, but want to merge the module first to allow for better parallelization of efforts around this project.
Why is it important?
Retrieve observability metrics for Enterprise Search. It will allow Monitoring plugin creation in Kibana, and Dashboards for retrieving metrics information from Enterprise Search.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
mage unitTest
Additional notes
Please note: There are some changes in this PR we had to make to improve the development experience (or enable it) on M1 macs and a few cosmetic changes to the code outside of our module. We have extracted those changes into separate PRs, but those PRs are still in review, so the changes are visible here as well:
These have been merged, so it is not an issue anymore.