opentelemetry-collector/receiver
Andrew Wilkins cc556e7df5
Bump minimum Go version to 1.24 (#13627)
#### Description

[Go 1.25.0](https://go.dev/doc/devel/release#go1.25.0) is released, time
to bump the minimum supported version.

#### Link to tracking issue

N/A

#### Testing

N/A

#### Documentation

Updated
2025-08-13 14:48:10 +00:00
..
internal [chore] Remove dead code from receiver internal (#12581) 2025-03-07 16:45:21 +00:00
nopreceiver Bump minimum Go version to 1.24 (#13627) 2025-08-13 14:48:10 +00:00
otlpreceiver Bump minimum Go version to 1.24 (#13627) 2025-08-13 14:48:10 +00:00
receiverhelper Bump minimum Go version to 1.24 (#13627) 2025-08-13 14:48:10 +00:00
receivertest Bump minimum Go version to 1.24 (#13627) 2025-08-13 14:48:10 +00:00
xreceiver Bump minimum Go version to 1.24 (#13627) 2025-08-13 14:48:10 +00:00
Makefile split receiver into its own module (#7195) 2023-03-02 12:04:58 -08:00
README.md [chore] Simplify general information in receivers/exporter readme (#9336) 2024-01-22 09:55:32 -08:00
doc.go [chore] Reorganize documentation regarding consumer errors for receiver (#12610) 2025-03-12 11:44:37 +00:00
example_test.go Add documentation example for receiver package (#5675) (#12922) 2025-04-30 10:17:35 +00:00
go.mod Bump minimum Go version to 1.24 (#13627) 2025-08-13 14:48:10 +00:00
go.sum Update module google.golang.org/protobuf to v1.36.7 (#13604) 2025-08-11 01:38:42 +00:00
package_test.go [chore] remove unused opencensus code (#9108) 2024-01-30 10:19:42 -08:00
receiver.go [chore] prevent unkeyed literal initialization (#12762) 2025-04-15 08:18:07 +00:00
receiver_test.go [chore]: fix testifylint rules (#12791) 2025-04-02 23:10:07 +00:00

README.md

General Information

A receiver is how data gets into the OpenTelemetry Collector. Generally, a receiver accepts data in a specified format, translates it into the internal format and passes it to processors and exporters defined in the applicable pipelines.

This repository hosts the following receiver available in traces, metrics and logs pipelines:

The contrib repository has more receivers available in its builds.

Configuring Receivers

Receivers are configured via YAML under the top-level receivers tag. There must be at least one enabled receiver for a configuration to be considered valid.

The following is a sample configuration for the examplereceiver.

receivers:
  # Receiver 1.
  # <receiver type>:
  examplereceiver:
    # <setting one>: <value one>
    endpoint: 1.2.3.4:8080
    # ...
  # Receiver 2.
  # <receiver type>/<name>:
  examplereceiver/settings:
    # <setting two>: <value two>
    endpoint: 0.0.0.0:9211

A receiver instance is referenced by its full name in other parts of the config, such as in pipelines. A full name consists of the receiver type, '/' and the name appended to the receiver type in the configuration. All receiver full names must be unique.

For the example above:

  • Receiver 1 has full name examplereceiver.
  • Receiver 2 has full name examplereceiver/settings.

Receivers are enabled upon being added to a pipeline. For example:

service:
  pipelines:
    # Valid pipelines are: traces, metrics or logs
    # Trace pipeline 1.
    traces:
      receivers: [examplereceiver, examplereceiver/settings]
      processors: []
      exporters: [exampleexporter]
    # Trace pipeline 2.
    traces/another:
      receivers: [examplereceiver, examplereceiver/settings]
      processors: []
      exporters: [exampleexporter]

At least one receiver must be enabled per pipeline to be a valid configuration.