Prepare the tenant, application, network path, and credentials before configuring an exporter.

Tenant and access

  • Trace Monitoring must be enabled for the OpsRamp client/tenant.
  • A user opening trace views needs the tenant entitlement and TRACE_VIEW access.
  • Restricted tracing setup instructions in the Observability UI may require INTEGRATION_MANAGE.
  • Ask a client administrator to enable the entitlement or grant access if the tracing views or setup instructions are unavailable.

Application and collection path

  • The application is configured with an OpenTelemetry SDK and emits spans with a stable service.name.
  • Plan to export OTLP spans from the manually instrumented application to the required OpsRamp trace proxy, optionally through an OpenTelemetry Collector.
  • Obtain the endpoint, protocol, tenant identifier, and authentication settings for that path from the tenant’s Trace Setup instructions.
  • Ensure the application or Collector can resolve and reach that endpoint on the required port. Confirm firewall, proxy, and TLS trust requirements with the platform owner.
  • Decide where credentials will be stored. Use a protected secret store or service configuration, not source code, images, or checked-in files.

Before production

Test connectivity and export in a non-production environment when available. Confirm which team owns the Collector or proxy, who can rotate its credentials, and how configuration changes are deployed.