> ## Documentation Index
> Fetch the complete documentation index at: https://otel.fyi/llms.txt
> Use this file to discover all available pages before exploring further.

# Wavefront

> OpenTelemetry receiver for Wavefront

# Wavefront Receiver

![Status](https://img.shields.io/badge/status-deprecated-lightgrey)

**Available in:** `contrib`

**Maintainers:** [@samiura](https://github.com/samiura)

**Source:** [opentelemetry-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/wavefrontreceiver)

## Supported Telemetry

![Metrics](https://img.shields.io/badge/metrics-deprecated-green)

## Overview

The Wavefront receiver accepts metrics and depends on [carbonreceiver proto
and
transport](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/carbonreceiver),
It's very similar to Carbon: it is TCP based in which each received text line
represents a single metric data point. They differ on the format of their
textual representation. The Wavefront receiver leverages the Carbon receiver
code by implementing a dedicated parser for its format.

The receiver receives the string with Wavefront metric data, and transforms
it to the collector metric format. See
[https://docs.wavefront.com/wavefront\_data\_format.html#metrics-data-format-syntax.](https://docs.wavefront.com/wavefront_data_format.html#metrics-data-format-syntax)
Each line received represents a Wavefront metric in the following format:

`<metricName> <metricValue> [<timestamp>] source=<source> [pointTags]`

> :information\_source: The `wavefront` receiver is based on Carbon and binds to the
> same port by default. This means the `carbon` and `wavefront` receivers
> cannot both be enabled with their respective default configurations. To
> support running both receivers in parallel, change the `endpoint` port on one
> of the receivers.

## Configuration

The following settings are required:

* `endpoint` (default = `0.0.0.0:2003`): Address and port that the
  receiver should bind to.

The following setting are optional:

* `extract_collectd_tags` (default = `false`): Instructs the Wavefront
  receiver to attempt to extract tags in the CollectD format from the
  metric name.
* `tcp_idle_timeout` (default = `30s`): The maximum duration that a tcp
  connection will idle wait for new data.

Example:

```yaml theme={null}
receivers:
  wavefront:
  wavefront/allsettings:
    endpoint: localhost:8080
    tcp_idle_timeout: 5s
    extract_collectd_tags: true
```

The full list of settings exposed for this receiver are documented in [config.go](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/wavefrontreceiver/config.go)
with detailed sample configurations in [testdata/config.yaml](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/wavefrontreceiver/testdata/config.yaml).

## Configuration

### Example Configuration

```yaml theme={null}
wavefront:
wavefront/allsettings:
  # endpoint specifies the network interface and port which will receive
  # Wavefront data.
  endpoint: localhost:8080
  # tcp_idle_timeout is max duration that a tcp connection will idle wait for
  # new data. The default value is 30 seconds.
  tcp_idle_timeout: 5s
  # extract_collectd_tags instructs the Wavefront receiver to attempt to extract
  # tags in the CollectD format from the metric name. The default is false.
  extract_collectd_tags: true
```

***

*Last generated: 2026-07-06*