Introduction

With Kubernetes 2.0 Agent, the Tracing Proxy is automatically installed when tracing is enabled for the cluster. This ensures seamless trace ingestion and management within the Kubernetes environment.

This document ensures a seamless setup process for users to enable trace ingestion with Kubernetes 2.0 agents.

Prerequisites

  1. Enable Trace Management at client level
    Ensure that the Client-level Trace Management feature is enabled. For more details, refer to Enable Traces document.
  2. Enable Traces during Agent installation
    • During installation of the Kubernetes 2.0 Agent, ensure that the Traces option is enabled.
    • For details, refer to the Agent Installation Guide.

If tracing is enabled, Helm automatically installs tracing-proxy pods with the specified replica count.

Configure Trace Ingestion

To enable trace ingestion, follow these steps:

  1. Instrument the application to send traces over gRPC or HTTP.
  2. Configure the following endpoints for trace ingestion:
    • gRPC Endpoint:
      opsramp-trace-service.opsramp-agent.svc.cluster.local:9090
    • HTTP Endpoint:
      opsramp-trace-service.opsramp-agent.svc.cluster.local:8082
  3. If you want to modify the listen ports of the trace proxy, update the respective endpoint using the following Helm command:
    --helm upgrade <release-name> <chart-name> --reuse-values --set traces.grpcPort=<port>  --set traces.httpPort=<port>

View Traces in OpsRamp Portal

  1. Navigate to Infrastructure > Traces in the OpsRamp portal.
    Event Management
  2. All available application traces will be listed on this page.
    Event Management
  3. Click on any application to view detailed trace information.
    Event Management

For more information on trace collection, refer to the Tracing