-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Update filtering documentation #2631
Conversation
cc @phemmer |
docs/CONFIGURATION.md
Outdated
* **namepass**: | ||
An array of strings that is used to filter metrics generated by the | ||
current input. Each string is tested as a glob match against measurement names | ||
and only if it matches, the field is emitted. |
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.
only if it matches, the
fieldis emitted
the point is emitted
docs/CONFIGURATION.md
Outdated
An array of strings that is used to filter metrics generated by the current | ||
input. Each string in the array is matched as a glob pattern against field | ||
names and if it matches, the field is emitted. `fieldpass` is not available | ||
for outputs. |
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.
Should note that only fields which match are emitted. All other fields will be dropped.
docs/CONFIGURATION.md
Outdated
`fielddrop` is not available for outputs. | ||
* **tagpass**: | ||
A table mapping tag keys to arrays of tag value patterns. Each pattern is | ||
matched as a glob against the corresponding tag key and if the point contains |
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.
the
correspondingtagkey
the tag value
And clarification why to omit "corresponding"
Each pattern is matched ...
There is only one tag value. So each pattern corresponds to what?
docs/CONFIGURATION.md
Outdated
pass an entire point based on its tag, `taginclude` passes only the specified | ||
tags from the measurement. This filter can be used on both inputs & outputs, | ||
but it is _recommended_ to be used on inputs, as it is more efficient to | ||
filter out tags at the ingestion point. |
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.
The description doesn't cover how to format the config param. An array of tag names to glob. non-matching tag is dropped.
I rewrote it all again. Made sure to start with the type of the field and tried to simplify/clarify. |
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.
Hooray for clear documentation! 👍
docs/CONFIGURATION.md
Outdated
The inverse of `namepass`. If a match is found the point is discarded. This | ||
is tested on points after they have passed the `namepass` test. | ||
* **fieldpass**: | ||
An array of glob pattern strings. Only fields whose field key matches an |
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.
Nit:
matches
an
matches a
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.
thanks
1bbc069
to
f8f546e
Compare
I tried to clarify some of the issues surrounding tagpass, reordered taginclude/tagexclude to match the other filters, and tried to correct some of the terminology.
Required for all PRs: