ITRS acquires IP-Label. Read the press release.

  1. Support
  2. Knowledge base
  3. OpenTelemetry
  4. Uptrends OpenTelemetry export prerequisites

Uptrends OpenTelemetry export prerequisites

Note: Uptrends OpenTelemetry export is available for Enterprise-level accounts.

Prerequisites

To export monitoring data from Uptrends, make sure the following prerequisites are met:

OpenTelemetry-capable platform

An OpenTelemetry collector or vendor connector that you configure and operate. Uptrends sends monitoring data to this connector, which forwards it to your observability platform. For example, Elastic, New Relic, Splunk, Prometheus, or ITRS Analytics.

Endpoint URL

Your connector must expose a secure HTTPS endpoint. Add this URL to the Uptrends OpenTelemetry export > Connections setting.

OpenTelemetry commonly uses port 4317 (gRPC). For example, https://otlp.eu01.nr-data.net:4317 is a valid endpoint URL. If no port is specified, port 443 is used by default.

Payload type

Uptrends supports the following transport types. Use the option supported by your connector and allowed by your network configuration:

  • gRPC
  • HTTP/Protobuf

Firewall configuration

Your connector must accept incoming traffic from Uptrends. Ensure your firewall allows:

  • Incoming HTTPS traffic
  • On the configured URL
  • On the specified port

Authentication

In the OpenTelemetry settings, configure any authentication details that apply:

  • Basic authentication — provide a username and password when the connector uses HTTP Basic Authentication.
  • Custom HTTP headers — provide a header name and value for token or API key authentication (for example, Authorization: Bearer <token>).

You may also securely store your credentials in the Uptrends Vault. For more information, see Uptrends Vault.

Setup and configuration

To get started, see the Uptrends OpenTelemetry export setup and configuration article.

By using the Uptrends website, you consent to the use of cookies in accordance with our Cookie Policy.