OpenTelemetry Collector for VictoriaMetrics

The OpenTelemetry Collector receives traces, metrics, and logs, processes the telemetry, and exports it to a wide variety of observability backends using its components. For a conceptual overview of the Collector, see Collector.

Usage

We have initialize a basic /etc/otelcol/config.yaml that has the following defaults:

• Have an OTLP gRPC receiver on port 4317 and an HTTP receiver on port 4318 for traces and logs.
  • There is no metrics receiver since Prometheus does not enable OTLP remote-write by default. If you prefer the OTLP metrics pattern, check this guide to enable OpenTelemetry for Prometheus, and you can configure the Prometheus receiver in the "/etc/otelcol/config.yaml" file.
• Export otel-collector metrics in Prometheus format on port 8888. You can scrape the metrics from this port.
• Export traces to VictoriaTraces and logs to VictoriaLogs.
• The health check endpoint is available at http://your-domain/health, where your-domain binds to port 13133.
• Limit the memory usage of the collector to 2GB.
• Enable the debug exporter to print the traces and logs to the console.

You should deploy VictoriaTraces and VictoriaLogs in the same project as this service. Configure your service to send traces and logs to this collector.

To customize the configuration, edit the /etc/otelcol/config.yaml file in the Config Editor. If you need further customization, refer to the Collector Configuration documentation. You can add more receivers like Jaeger, exporters like Prometheus, or processors like filter.

Add metrics to your VictoriaMetrics

Add the following target to your /etc/victoriametrics/scrape.yaml file of your VictoriaMetrics instance:

scrape_configs:
  - job_name: 'otel-collector'
    static_configs:
      - targets: ['http://otel-collector:8888/metrics']