Skip to content

Commit

Permalink
Remove "resource_attributes" from readme.
Browse files Browse the repository at this point in the history
Add "attributes" and "libraries" as invalid metrics filters.
  • Loading branch information
ptodev authored and jpkrohling committed May 23, 2023
1 parent 9ba2273 commit 9087fd0
Showing 1 changed file with 13 additions and 14 deletions.
27 changes: 13 additions & 14 deletions processor/attributesprocessor/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -181,20 +181,19 @@ Metric transform processor specific functionality

## Include/Exclude Filtering

The [attribute processor](README.md) exposes
an option to provide a set of properties of a span, log, or metric record to match against to determine
if the input data should be included or excluded from the processor. To configure
this option, under `include` and/or `exclude` at least `match_type` and one of the following
is required:
- For spans, one of `services`, `span_names`, `span_kinds`, `attributes`, `resources`, or `libraries` must be specified
with a non-empty value for a valid configuration. The `log_bodies`, `log_severity_texts`, `log_severity_number`,
`resource_attributes` and `metric_names` fields are invalid.
- For logs, one of `log_bodies`, `log_severity_texts`, `log_severity_number`, `attributes`, `resources`, or `libraries`
must be specified with a non-empty value for a valid configuration. The `span_names`, `span_kinds`, `metric_names`,
`resource_attributes`, and `services` fields are invalid.
- For metrics, one of `metric_names`, `resources` must be specified
with a valid non-empty value for a valid configuration. The `span_names`, `span_kinds`, `log_bodies`, `log_severity_texts`,
`log_severity_number` and `services` fields are invalid.
The [attribute processor](README.md) exposes an option to provide a set of properties of a span, log
or metric record to match against to determine if the input data should be included or excluded from
the processor. To configure this option, under `include` and/or `exclude` at least `match_type` and
one of the following is required:
- For spans, one of `services`, `span_names`, `span_kinds`, `attributes`, `resources` or `libraries`
must be specified with a non-empty value for a valid configuration. The `log_bodies`, `log_severity_texts`,
`log_severity_number` and `metric_names` fields are invalid.
- For logs, one of `log_bodies`, `log_severity_texts`, `log_severity_number`, `attributes`, `resources`
or `libraries` must be specified with a non-empty value for a valid configuration. The `span_names`,
`span_kinds`, `metric_names` and `services` fields are invalid.
- For metrics, one of `metric_names` or `resources` must be specified with a valid non-empty value for
a valid configuration. The `span_names`, `span_kinds`, `log_bodies`, `log_severity_texts`,
`log_severity_number`, `services`, `attributes` and `libraries` fields are invalid.


Note: If both `include` and `exclude` are specified, the `include` properties
Expand Down

0 comments on commit 9087fd0

Please sign in to comment.