CL-Softwares
/
telegraf
8
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: revert table example change (#13556)

This commit is contained in:
Joshua Powers 2023-07-05 16:22:02 -06:00 committed by GitHub
parent f0f454d24f
commit 22bfb405bb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/CONFIGURATION.md
View File

@ -619,9 +619,9 @@ is tested on metrics after they have passed the `namepass` test.
- **tagpass**: - **tagpass**:
A table mapping tag keys to arrays of [glob pattern][] strings. Only metrics A table mapping tag keys to arrays of [glob pattern][] strings. Only metrics
that contain a tag key in the table and a tag value matching one of its that contain a tag key in the table and a tag value matching one of its
patterns is emitted. This can either use the explicit table synax (e.g. patterns is emitted. This can either use the explicit table syntax (e.g.
a subsection using a `[...]` header) or inline table syntax (e.g like a subsection using a `[...]` header) or inline table syntax (e.g like
a JSON table with `{...}`. a JSON table with `{...}`). Please see the below notes on specifying the table.
- **tagdrop**: - **tagdrop**:
The inverse of `tagpass`. If a match is found the metric is discarded. This The inverse of `tagpass`. If a match is found the metric is discarded. This
@ -631,8 +631,11 @@ is tested on metrics after they have passed the `tagpass` test.
> syntax (with `[...]`) for `tagpass` and `tagdrop` parameters, they > syntax (with `[...]`) for `tagpass` and `tagdrop` parameters, they
> must be defined at the **end** of the plugin definition, otherwise subsequent > must be defined at the **end** of the plugin definition, otherwise subsequent
> plugin config options will be interpreted as part of the tagpass/tagdrop > plugin config options will be interpreted as part of the tagpass/tagdrop
> tables. This limitation does not apply when using the inline table > tables.
> syntax (`{...}`).
> NOTE: When using the inline table syntax (e.g. `{...}`) the table must exist
> in the main plugin definition and not in any sub-table (e.g.
> `[[inputs.win_perf_counters.object]]`).
- **metricpass**: - **metricpass**:
A ["Common Expression Language"][CEL] (CEL) expression with boolean result where A ["Common Expression Language"][CEL] (CEL) expression with boolean result where
@ -712,9 +715,10 @@ tags and the agent `host` tag.
"Bytes Sent/sec" "Bytes Sent/sec"
] ]
Measurement = "win_net" Measurement = "win_net"
# Don't send metrics where the Windows interface name (instance) begins with isatap or Local # Do not send metrics where the Windows interface name (instance) begins with
# This illustrates the inline table syntax # 'isatap' or 'Local'
tagdrop = {instance = ["isatap*", "Local*"]} [inputs.win_perf_counters.tagdrop]
instance = ["isatap*", "Local*"]
``` ```
#### Using fieldpass and fielddrop #### Using fieldpass and fielddrop