-
Notifications
You must be signed in to change notification settings - Fork 4.9k
filebeat: remove usages of inputmon.NewInputRegistry #43862
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
base: main
Are you sure you want to change the base?
filebeat: remove usages of inputmon.NewInputRegistry #43862
Conversation
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
49c4b20
to
3009090
Compare
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.
Copilot reviewed 57 out of 58 changed files in this pull request and generated no comments.
Files not reviewed (1)
- CHANGELOG-developer.next.asciidoc: Language not supported
Comments suppressed due to low confidence (4)
x-pack/filebeat/input/awss3/metrics.go:79
- The un-register call has been removed from the Close() method; please verify that metrics registry cleanup is handled elsewhere to prevent any resource leaks.
m.unregister()
filebeat/input/unix/input.go:144
- Ensure that the v2.Context passed to newInputMetrics includes a valid non-empty ID so that the metrics are properly initialized and not returned as nil.
if ctx.ID == "" {
filebeat/input/netmetrics/udp.go:57
- Confirm that the v2.Context provided to NewUDP includes a non-empty ID to guarantee that the metricset is created as expected.
if ctx.ID == "" {
filebeat/input/netmetrics/tcp.go:55
- Make sure the v2.Context passed to NewTCP contains a valid ID to prevent the metrics from being nil and to ensure proper runtime behavior.
if ctx.ID == "" {
9aaafd3
to
766ced4
Compare
58f36f1
to
fc8ad51
Compare
Proposed commit message
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
.Disruptive User Impact
How to test this PR locally
Related issues