Configure Telemetry Gateway forwarding (optional)

Configure the Telemetry Gateway to forward device telemetry to an upstream OTLP/gRPC backend over mutual TLS, in addition to local Prometheus scraping.

Before you begin

  • A client certificate, private key, and upstream CA certificate file are available for mutual TLS with the upstream OTLP gRPC endpoint.
  • The upstream OTLP gRPC endpoint address and port are known.

About this task

By default, the Telemetry Gateway exports metrics for local Prometheus scraping. You can optionally configure forwarding to send telemetry data to an upstream OTLP/gRPC backend.

Use forwarding when you:

  • Have an existing observability infrastructure (for example, Grafana Cloud, Datadog, or New Relic).
  • Want to centralize telemetry from multiple Red Hat Edge Manager deployments.
  • Need to integrate with organization-wide monitoring systems.

Procedure

  1. Place the client certificate and key in the forward directory: 
    sudo install -o root -g root -m 644 /path/to/client-cert.crt \
  /etc/flightctl/flightctl-telemetry-gateway/forward/client.crt
sudo install -o root -g root -m 600 /path/to/client-key.key \
  /etc/flightctl/flightctl-telemetry-gateway/forward/client.key
  2. Place the upstream CA certificate: 
    sudo install -o root -g root -m 644 /path/to/upstream-ca.crt \
  /etc/flightctl/flightctl-telemetry-gateway/forward/ca.crt
  3. Edit /etc/flightctl/service-config.yaml to configure the forwarding endpoint: 
    telemetryGateway:
  forward:
    endpoint: otlp.example.com:4317
    tls:
      insecureSkipTlsVerify: false
      caFile: /etc/flightctl/flightctl-telemetry-gateway/forward/ca.crt
      certFile: /etc/flightctl/flightctl-telemetry-gateway/forward/client.crt
      keyFile: /etc/flightctl/flightctl-telemetry-gateway/forward/client.key
  4. Restart the telemetry gateway: 
    sudo systemctl restart flightctl-telemetry-gateway.service

Results

  1. Check the telemetry gateway logs to verify successful forwarding: 
    sudo journalctl -u flightctl-telemetry-gateway.service -f
  2. Look for log entries that indicate successful OTLP exports, similar to the following example: 
    {"level":"info","msg":"Successfully forwarded metrics batch","endpoint":"otlp.example.com:4317","batch_size":100}