Caution
Grafana Agent has reached End-of-Life (EOL) on November 1, 2025. Agent is no longer receiving vendor support and will no longer receive security or bug fixes. Current users of Agent Static mode, Agent Flow mode, and Agent Operator should proceed with migrating to Grafana Alloy. If you have already migrated to Alloy, no further action is required. Read more about why we recommend migrating to Grafana Alloy.
Important: This documentation is about an older version. It's relevant only to the release noted, many of the features and functions have been updated or replaced. Please view the current version.
otelcol.receiver.jaeger
otelcol.receiver.jaeger accepts Jaeger-formatted data over the network and
forwards it to other otelcol.* components.
NOTE:
otelcol.receiver.jaegeris a wrapper over the upstream OpenTelemetry Collectorjaegerreceiver. Bug reports or feature requests will be redirected to the upstream repository, if necessary.
Multiple otelcol.receiver.jaeger components can be specified by giving them
different labels.
Usage
otelcol.receiver.jaeger "LABEL" {
protocols {
grpc {}
thrift_http {}
thrift_binary {}
thrift_compact {}
}
output {
metrics = [...]
logs = [...]
traces = [...]
}
}Arguments
otelcol.receiver.jaeger doesn’t support any arguments and is configured fully
through inner blocks.
Blocks
The following blocks are supported inside the definition of
otelcol.receiver.jaeger:
The > symbol indicates deeper levels of nesting. For example, protocols > grpc refers to a grpc block defined inside a protocols block.
protocols block
The protocols block defines a set of protocols that will be used to accept
traces over the network.
protocols doesn’t support any arguments and is configured fully through inner
blocks.
otelcol.receiver.jeager requires at least one protocol block (grpc,
thrift_http, thrift_binary, or thrift_compact) to be provided.
grpc block
The grpc block configures a gRPC server which can accept Jaeger traces. If
the grpc block isn’t provided, a gRPC server isn’t started.
The following arguments are supported:
tls block
The tls block configures TLS settings used for a server. If the tls block
isn’t provided, TLS won’t be used for connections to the server.
The following arguments are supported:
keepalive block
The keepalive block configures keepalive settings for connections to a gRPC
server.
keepalive doesn’t support any arguments and is configured fully through inner
blocks.
server_parameters block
The server_parameters block controls keepalive and maximum age settings for gRPC
servers.
The following arguments are supported:
enforcement_policy block
The enforcement_policy block configures the keepalive enforcement policy for
gRPC servers. The server will close connections from clients that violate the
configured policy.
The following arguments are supported:
thrift_http block
The thrift_http block configures an HTTP server which can accept
Thrift-formatted traces. If the thrift_http block isn’t specified, an HTTP
server isn’t started.
The following arguments are supported:
cors block
The cors block configures CORS settings for an HTTP server.
The following arguments are supported:
The allowed_headers specifies which headers are acceptable from a CORS
request. The following headers are always implicitly allowed:
AcceptAccept-LanguageContent-TypeContent-Language
If allowed_headers includes "*", all headers will be permitted.
thrift_binary block
The thrift_binary block configures a UDP server which can accept traces
formatted to the Thrift binary protocol. If the thrift_binary block isn’t
provided, a UDP server isn’t started.
The following arguments are supported:
thrift_compact block
The thrift_compact block configures a UDP server which can accept traces
formatted to the Thrift compact protocol. If the thrift_compact block isn’t
provided, a UDP server isn’t started.
The following arguments are supported:
output block
The output block configures a set of components to forward resulting
telemetry data to.
The following arguments are supported:
The output block must be specified, but all of its arguments are optional. By
default, telemetry data is dropped. To send telemetry data to other components,
configure the metrics, logs, and traces arguments accordingly.
Exported fields
otelcol.receiver.jaeger does not export any fields.
Component health
otelcol.receiver.jaeger is only reported as unhealthy if given an invalid
configuration.
Debug information
otelcol.receiver.jaeger does not expose any component-specific debug
information.
Example
This example creates a pipeline which accepts Jaeger-formatted traces and writes them to an OTLP server:
otelcol.receiver.jaeger "default" {
protocols {
grpc {}
thrift_http {}
thrift_binary {}
thrift_compact {}
}
output {
traces = [otelcol.processor.batch.default.input]
}
}
otelcol.processor.batch "default" {
output {
traces = [otelcol.exporter.otlp.default.input]
}
}
otelcol.exporter.otlp "default" {
client {
endpoint = "my-otlp-server:4317"
}
}


