This page guides where to place exporter settings for common runtime environments. They assume an application already emits spans through an OpenTelemetry SDK.

Common setup

  1. Enable Trace Monitoring and obtain the tenant-specific endpoint and credentials.
  2. Choose an application-to-proxy or Collector-to-proxy layout. The OpsRamp trace proxy is required in both layouts.
  3. Set a stable service name and the OTLP protocol supported by the selected endpoint.
  4. Store secrets in the environment’s secret-management facility and pass only the required settings to the workload.
  5. Deploy or restart the application so its SDK uses the updated settings.
  6. Send a representative request and verify trace ingestion.

For a trace-proxy deployment, the product setup documentation lists default in-cluster listeners at gRPC port 9090 and HTTP port 8082; host-based examples use the proxy server address with those ports. Confirm the actual listener, DNS name, TLS termination, and required headers in the tenant’s Trace Setup instructions before use.

Choose an environment

  • Kubernetes: configure workload settings and secrets in the cluster.
  • Linux VM / Bare Metal: configure the application service environment.
  • Windows Server: configure the application process or Windows service.
  • Containers (Docker): pass settings when starting the container, not in the image.
  • Serverless: use provider-managed configuration and secrets, and account for runtime egress and shutdown behavior.

Variable names and endpoint syntax can vary across language SDKs. Use the selected SDK’s documentation together with the tenant-specific OpsRamp setup instructions.