-
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
fix: Tag filters only allow single values per key #32775
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
|
thanks for your contribution! this seems like a reasonable enhancement to me. do you have thoughts @ravikesarwani ? before we can merge we need a few things sorting:
thanks! |
60e5ac2
to
290114b
Compare
The more I think about this, the more i realize that this might be a bigger problem. There is no way to distinguish between AND and OR logic with the filters I think is the real problem. Any advice? |
b26ff63
to
e10634c
Compare
This pull request is now in conflicts. Could you fix it? 🙏
|
b65e355
to
bb829af
Compare
f6150c9
to
a719f49
Compare
a719f49
to
83dd433
Compare
💚 CLA has been signed |
097a84d
to
d31cee4
Compare
d31cee4
to
9b3343a
Compare
@cjr125 it seems you force pushed a previous commit without the latest changes |
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.
force push without approved changes
9b3343a
to
9a2f093
Compare
fixed |
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
9a2f093
to
c2239e0
Compare
When filtering tags from the AWS Metricbeat module, it is not possible to specify more than one value associated to a particular key. A practical example of this would be filtering for more than one development environment (among others) on a single instance of Metricbeat.
c2239e0
to
9c83f53
Compare
@cjr125 all good on my side can you please sign the CLA? |
9c83f53
to
384da88
Compare
* fix: Tag filters only allow single values per key When filtering tags from the AWS Metricbeat module, it is not possible to specify more than one value associated to a particular key. A practical example of this would be filtering for more than one development environment (among others) on a single instance of Metricbeat. * Expand Unit Test Coverage * Updated changelog (cherry picked from commit 3e07726)
* fix: Tag filters only allow single values per key When filtering tags from the AWS Metricbeat module, it is not possible to specify more than one value associated to a particular key. A practical example of this would be filtering for more than one development environment (among others) on a single instance of Metricbeat. * Expand Unit Test Coverage * Updated changelog (cherry picked from commit 3e07726) Co-authored-by: cjr125 <croberts1@gmail.com>
* fix: Tag filters only allow single values per key When filtering tags from the AWS Metricbeat module, it is not possible to specify more than one value associated to a particular key. A practical example of this would be filtering for more than one development environment (among others) on a single instance of Metricbeat. * Expand Unit Test Coverage * Updated changelog
What does this PR do?
When filtering tags from the AWS Metricbeat module, it is not possible to specify more than one value associated to a particular key. This PR allows for that.
Why is it important?
A practical example of this would be filtering for more than one development environment (among others) on a single instance of Metricbeat.
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Try loading the following AWS module config into Metricbeat: