-
Notifications
You must be signed in to change notification settings - Fork 540
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?
Changes from 3 commits
cd45857
4bff80f
a391c5e
ce52150
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -14,6 +14,7 @@ | |
| | `Bucket` | InfluxDB bucket name where records will be inserted. If specified, `database` is ignored and v2 of API is used. | _none_ | | ||
| | `Org` | InfluxDB organization name where the bucket is (v2 only). | `fluent` | | ||
| | `Sequence_Tag` | The name of the tag whose value is incremented for the consecutive simultaneous events. | `_seq` | | ||
| | `Strip_Prefix` | String to be stripped from the front of `tag` when writing influxdb measurement names. | _none_ | | ||
|
Check warning on line 17 in pipeline/outputs/influxdb.md
|
||
| | `HTTP_User` | Optional username for HTTP Basic Authentication. | _none_ | | ||
| | `HTTP_Passwd` | Password for user defined in `HTTP_User`. | _none_ | | ||
| | `HTTP_Token` | Authentication token used with InfluxDB v2. If specified, both `HTTP_User` and `HTTP_Passwd` are ignored. | _none_ | | ||
|
|
@@ -191,6 +192,43 @@ | |
| {% endtab %} | ||
| {% endtabs %} | ||
|
|
||
| ### Prefix stripping | ||
|
|
||
| When collecting data from many inputs into many buckets, it can be helpful to remove a common prefix using `Strip_prefix`. | ||
|
|
||
| ```python | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we should be using the recently made default approach of having both configs (YAML and legacy) in place. |
||
| [INPUT] | ||
| Name cpu | ||
| Tag cpu.one | ||
|
|
||
| [INPUT] | ||
| Name cpu | ||
| Tag cpu.two | ||
|
|
||
| [INPUT] | ||
| Name cpu | ||
| Tag gpu.one | ||
|
|
||
| [INPUT] | ||
| Name cpu | ||
| Tag gpu.two | ||
|
|
||
| [OUTPUT] | ||
| Name influxdb | ||
| Match cpu* | ||
| Bucket cpubucket | ||
| Strip_prefix cpu. | ||
|
|
||
| [OUTPUT] | ||
| Name influxdb | ||
| Match gpu* | ||
| Bucket gpubucket | ||
| Strip_prefix gpu. | ||
| ``` | ||
|
|
||
| This will result in the buckets `cpubucket` and `gpubucket` each containing two measurement streams named `one` and `two`. Without prefix stripping, the measurement names would be `cpu.one` and `cpu.two (stored in `cpubucket`), and `gpu.one`, `gpu.two` (stored in `gpubucket`). | ||
|
Check warning on line 229 in pipeline/outputs/influxdb.md
|
||
esmerel marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
|
|
||
| ### Testing | ||
|
|
||
| Before starting Fluent Bit, ensure the target database exists on InfluxDB. Using the previous example, insert the data into a `fluentbit` database. | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.