zooqueen
2483819907
A dependency bump reached the go.sum files but not the go.mod files: 27 modules still required go.uber.org/zap v1.27.1 while their go.sum carried only v1.28.0. Go then refused to build them at all — 43 modules answered `go list ./...` with "updates to go.mod needed" or "missing go.sum entry". They went unnoticed because every one of them sorts after cmd/otelcorecol, and gotest walks the modules in sorted order and stops at the first error, so the walk never reached them. Adding the missing sums to the four modules before that point moves the wall without removing it. Ran the tree's own tidy in every module, pinning each module's existing go directive so the local toolchain cannot raise it. cmd/otelcorecol is generated and carries a DO-NOT-EDIT header, so its result was checked against `make genotelcorecol`: byte-identical, go.mod and go.sum both. The rest is the convergence that bump implied — zap 1.27.1 -> 1.28.0, otel 1.40 -> 1.45, grpc 1.79.1 -> 1.80.0 and the x/ packages that follow them. Two requirements were missing outright (hashicorp/golang-lru/v2, go.yaml.in/yaml/v2) and configgrpc gained the root collector module it already replaces locally. mostynb/go-grpc-compression leaves the graph; no .go file imports it. go list ./... is clean in all 118 modules and no go directive moved.
Connectors
A connector is both an exporter and receiver. As the name suggests a Connector connects two pipelines: it emits data as an exporter at the end of one pipeline and consumes data as a receiver at the start of another pipeline. It may consume and emit data of the same data type, or of different data types. A connector may generate and emit data to summarize the consumed data, or it may simply replicate or route data.
Supported Data Types
Each type of connector is designed to work with one or more pairs of data types and may only be used to connect pipelines accordingly. (Recall that every pipeline is associated with a single data type, either traces, metrics, or logs.)
For example, the count connector counts traces, metrics, and logs, and reports the counts as a
metric. Therefore, it may be used to connect the following types of pipelines.
| Exporter Pipeline Type | Receiver Pipeline Type |
|---|---|
| traces | metrics |
| metrics | metrics |
| logs | metrics |
Another example, the router connector, is useful for routing data onto the appropriate pipeline
so that it may be processed in distinct ways and/or exported to an appropriate backend. It does not
alter the data it consumes in any ways, nor does it produce any additional data. Therefore, it may be
used to connect the following types of pipelines.
| Exporter Pipeline Type | Receiver Pipeline Type |
|---|---|
| traces | traces |
| metrics | metrics |
| logs | logs |
Configuration
Declaration
Connectors are defined within a dedicated connectors section at the top level of the collector config.
The count connector may be used with default settings.
receivers:
foo:
exporters:
bar:
connectors:
count:
router:
Usage
Recall that a connector is an exporter and a receiver and that each connector MUST be used as both, in separate pipelines.
receivers:
foo:
exporters:
bar:
connectors:
count:
service:
pipelines:
traces:
receivers: [foo]
exporters: [count]
metrics:
receivers: [count]
exporters: [bar]
Connectors can be used alongside traditional exporters.
receivers:
foo:
exporters:
bar/traces_backend:
bar/metrics_backend:
connectors:
count:
service:
pipelines:
traces:
receivers: [foo]
exporters: [bar/traces_backend, count]
metrics:
receivers: [count]
exporters: [bar/metrics_backend]
Connectors can be used alongside traditional receivers.
receivers:
foo/traces:
foo/metrics:
exporters:
bar:
connectors:
count:
service:
pipelines:
traces:
receivers: [foo/traces]
exporters: [count]
metrics:
receivers: [foo/metrics, count]
exporters: [bar]
A connector can be an exporter in multiple pipelines.
receivers:
foo/traces:
foo/metrics:
foo/logs:
exporters:
bar/traces_backend:
bar/metrics_backend:
bar/logs_backend:
connectors:
count:
service:
pipelines:
traces:
receivers: [foo/traces]
exporters: [bar/traces_backend, count]
metrics:
receivers: [foo/metrics]
exporters: [bar/metrics_backend, count]
logs:
receivers: [foo/logs]
exporters: [bar/logs_backend, count]
metrics/counts:
receivers: [count]
exporters: [bar/metrics_backend]
A connector can be a receiver in multiple pipelines.
receivers:
foo/traces:
foo/metrics:
exporters:
bar/traces_backend:
bar/metrics_backend:
bar/metrics_backend/2:
connectors:
count:
service:
pipelines:
traces:
receivers: [foo/traces]
exporters: [bar/traces_backend, count]
metrics:
receivers: [count]
exporters: [bar/metrics_backend]
metrics/2:
receivers: [count]
exporters: [bar/metrics_backend/2]
Multiple connectors can be used in sequence.
receivers:
foo:
exporters:
bar:
connectors:
count:
count/the_counts:
service:
pipelines:
traces:
receivers: [foo]
exporters: [count]
metrics:
receivers: [count]
exporters: [bar/metrics_backend, count/the_counts]
metrics/count_the_counts:
receivers: [count/the_counts]
exporters: [bar]
A connector can only be used in a pair of pipelines when it supports the combination of Exporter Pipeline Type and Receiver Pipeline Type.
receivers:
foo:
exporters:
bar:
connectors:
count:
service:
pipelines:
traces:
receivers: [foo]
exporters: [count]
logs:
receivers: [count] # Invalid. The count connector does not support traces -> logs.
exporters: [bar]
Exporter Pipeline Type
The type of pipeline in which a connector is used as an exporter.
Receiver Pipeline Type
The type of pipeline in which the connector is used as a receiver.