-
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
[Bug] fix bug with empty filter values returning no results in system/service #19812
[Bug] fix bug with empty filter values returning no results in system/service #19812
Conversation
Pinging @elastic/integrations (Team:Integrations) |
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
…/service (elastic#19812) * fix bug with empty filter values returning no results * add changelog entry (cherry picked from commit a1dd2ec)
…/service (elastic#19812) * fix bug with empty filter values returning no results * add changelog entry (cherry picked from commit a1dd2ec)
…/service (elastic#19812) * fix bug with empty filter values returning no results * add changelog entry
…/service (elastic#19812) (elastic#19914) * fix bug with empty filter values returning no results * add changelog entry (cherry picked from commit 1e531b1)
What does this PR do?
This fixes a bug where if the system/service module is running on an OS with an older version of systemd, and a user hasn't configured
pattern_filter
, the metricset will return no results. When using the systemdListUnitsFiltered
API call, we don't bypass the pattern_filter in cases where the filter is empty.Why is it important?
It's a bug, the metricset won't return any data.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
system/service
metricsetservice.pattern_filter
isn't configured.