-
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
[Oracle Module] Refactor module to properly use host parsers instead of doing its own parsing of hosts #31692
[Oracle Module] Refactor module to properly use host parsers instead of doing its own parsing of hosts #31692
Conversation
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 a small comment.
Rest LGTM!
Please wait for the others approvals.
…le_refactor_host_parsing
…-elastic/beats into oracle_refactor_host_parsing
This pull request is now in conflicts. Could you fix it? 🙏
|
…le_refactor_host_parsing
This pull request is now in conflicts. Could you fix it? 🙏
|
…le_refactor_host_parsing
This pull request is now in conflicts. Could you fix it? 🙏
|
Please revisit the testing.go. |
As a part of this PR, we are refactoring the host parsing mechanism of the Oracle Module, and based on our analysis, there does not seem to be a change required in the tests with respect to the changes we have made in the module. The |
This pull request is now in conflicts. Could you fix it? 🙏
|
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.
Looks good to me.
…of doing its own parsing of hosts (#31692) * Update host parsing mechanism * Update comment to add more description * Add CHANGELOG.next.asciidoc entry * Update CHANGELOG.next.asciidoc to remove accidentally added PRs
What does this PR do?
Refactors the Oracle module to properly use host parsers instead of doing its own parsing of hosts.
Why is it important?
Metricbeat should instantiate one metricset per host, and the metricset shouldn't need to do any special handling to support multiple hosts. Using
HostData
is the only way a metricset instance has to know what host to use when multiple hosts are configured. When parsing the configured host, it allows to set in theHostData
the Host, that is later used forservice.address
. It abstracts the handling of multiple hosts, each metricset instance receives a singleHostData
with the host they have to use.Checklist
- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues