Open source


otelcol.exporter.logging accepts telemetry data from other otelcol components and writes them to the console.

This component writes logs at the info level. The logging config block must be configured to write logs at the info level.

NOTE: otelcol.exporter.logging is a wrapper over the upstream OpenTelemetry Collector logging exporter. Bug reports or feature requests will be redirected to the upstream repository, if necessary.

Multiple otelcol.exporter.logging components can be specified by giving them different labels.


otelcol.exporter.logging "LABEL" { }


otelcol.exporter.logging supports the following arguments:

verbositystringVerbosity of the generated logs."normal"no
sampling_initialintNumber of messages initially logged each second.2no
sampling_thereafterintSampling rate after the initial messages are logged.500no

The verbosity argument must be one of "basic", "normal", or "detailed".

Exported fields

The following fields are exported and can be referenced by other components:

inputotelcol.ConsumerA value that other components can use to send telemetry data to.

input accepts otelcol.Consumer data for any telemetry signal (metrics, logs, or traces).

Component health

otelcol.exporter.logging is only reported as unhealthy if given an invalid configuration.

Debug information

otelcol.exporter.logging does not expose any component-specific debug information.


This example scrapes prometheus unix metrics and writes them to the console:

prometheus.exporter.unix { }

prometheus.scrape "default" {
	targets    = prometheus.exporter.unix.targets
	forward_to = [otelcol.receiver.prometheus.default.receiver]

otelcol.receiver.prometheus "default" {
	output {
		metrics = [otelcol.exporter.logging.default.input]

otelcol.exporter.logging "default" {
	verbosity           = "detailed"
	sampling_initial    = 1
	sampling_thereafter = 1