Skip to content
Permalink

Comparing changes

This is a direct comparison between two commits made in this repository or its related repositories. View the default comparison for this range or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: open-telemetry/opentelemetry-collector-contrib
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: ec754578647d4fbb89e9b14880960fa309de1fea
Choose a base ref
..
head repository: open-telemetry/opentelemetry-collector-contrib
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 589483344cd57e4beacc783123e4fc80b022336b
Choose a head ref
Showing with 6 additions and 4 deletions.
  1. +6 −4 connector/routingconnector/README.md
10 changes: 6 additions & 4 deletions connector/routingconnector/README.md
Original file line number Diff line number Diff line change
@@ -33,12 +33,13 @@ If you are not already familiar with connectors, you may find it helpful to firs
The following settings are available:

- `table (required)`: the routing table for this connector.
- `table.context (optional, default: resource)`: the [OTTL Context] in which the statement will be evaluated. Currently, only `resource` and `log` are supported.
- `table.statement`: the routing condition provided as the [OTTL] statement. Required if `table.condition` is not provided.
- `table.condition`: the routing condition provided as the [OTTL] condition. Required if `table.statement` is not provided.
- `table.pipelines (required)`: the list of pipelines to use when the routing condition is met.
- `default_pipelines (optional)`: contains the list of pipelines to use when a record does not meet any of specified conditions.
- `error_mode (optional)`: determines how errors returned from OTTL statements are handled. Valid values are `propagate`, `ignore` and `silent`. If `ignore` or `silent` is used and a statement's condition has an error then the payload will be routed to the default pipelines. When `silent` is used the error is not logged. If not supplied, `propagate` is used.
- `match_once (optional, default: false)`: determines whether the connector matches multiple statements or not. If enabled, the payload will be routed to the first pipeline in the `table` whose routing condition is met.
- `match_once (optional, default: false)`: determines whether the connector matches multiple statements or not. If enabled, the payload will be routed to the first pipeline in the `table` whose routing condition is met. May only be `false` when used with `resource` context.

Example:

@@ -109,10 +110,11 @@ Respectively, if none of the routing conditions met, then a signal is routed to
The full list of settings exposed for this connector are documented [here](./config.go) with detailed sample configuration files:
- [logs](./testdata/config_logs.yaml)
- [metrics](./testdata/config_metrics.yaml)
- [traces](./testdata/config_traces.yaml)
- [logs](./testdata/config/logs.yaml)
- [metrics](./testdata/config/metrics.yaml)
- [traces](./testdata/config/traces.yaml)
[Connectors README]:https://github.com/open-telemetry/opentelemetry-collector/blob/main/connector/README.md
[OTTL]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/ottl/README.md
[OTTL Context]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/ottl/LANGUAGE.md#contexts