-
Couldn't load subscription status.
- Fork 538
out_influxdb: documentation for tag prefix stripping #1468
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: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Ueli Graf <[email protected]>
Signed-off-by: Ueli Graf <[email protected]>
|
@fluent/chronosphere-tech-writers should we be ensuring we add YAML config as well now always? |
|
@esmerel can you review please, but leave open as code PR fluent/fluent-bit#9427 must merge first and is still open. |
|
@ueli-g can you resolve the conflicts and provide YAML config example (if you need help with that, happy to provide)? I also nudged you on the code PR fluent/fluent-bit#9427 |
Signed-off-by: Lynette Miles <[email protected]>
|
I fixed the merge conflicts and made review updates while I was fixing it since I was already in there. |
Signed-off-by: Lynette Miles <[email protected]>
Documentation to go with fluent/fluent-bit#9427
This removes a defined prefix from measurement names which might otherwise be shared between many measurements in the same data bucket. Compatibility is not affected, default behavior (with documented default strip_prefix "") is to strip zero character from the front which identical to the existing mechanism.
When writing to a range of different buckets, routing to the corresponding out_influxdb instances happens on tag matches. This change allows to match on tag prefixes, but strip them from the measurement name. This avoids having identical prefixes for all measurement names in the same data bucket.
To achieve this, read from char tag[] with an offset when writing the measurement name, provided the prefix matches the tag completely and the overlap is at most tag_length - 1 characters.