# 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](../processor/README.md) and [exporters](../exporter/README.md) defined in the applicable pipelines. Available trace receivers (sorted alphabetically): - [OTLP Receiver](otlpreceiver/README.md) Available metric receivers (sorted alphabetically): - [OTLP Receiver](otlpreceiver/README.md) Available log receivers (sorted alphabetically): - [OTLP Receiver](otlpreceiver/README.md) The [contrib repository](https://github.com/open-telemetry/opentelemetry-collector-contrib) has more receivers that can be added to custom builds of the collector. ## 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`. ```yaml receivers: # Receiver 1. # : examplereceiver: # : endpoint: 1.2.3.4:8080 # ... # Receiver 2. # /: examplereceiver/settings: # : 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: ```yaml 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.