This section describes downloading and installing the trace proxy in various platforms and also pointing to your trace instrumented application.
Follow the steps below for more information on trace collection:
Log in to OpsRamp Portal.
Navigate to Infrastructure > Traces.
On the Traces Configuration page, click LET’S GET STARTED.
You can also access the Traces Configuration from the Menu icon on the left side of this page as shown below.
Follow the instructions to set up the trace collection under the Set up Traces Collection section.
At present, OpsRamp supports two types of environments where you can setup the trace proxy: Kubernetes and Host Based.
Configure Trace proxy
This section details about configuring the trace proxy based on user needs. The trace proxy consists of three main resources:
- Listener: The purpose of a listener is to collect, store, and route tracing messages. Listeners direct the tracing output to an appropriate target, such as a down sampler.
- Down Sampler: As a trace is a representation of the life cycle of a particular operation, most of the data may not be useful to the user. The downsampling is the process of reducing the sampling rate of the data received from the listener. The trace proxy handles the task of downsampling all the traces to reduce the traffic in the portal.
- Exporter: Each time when a trace span arrives at the exporter, the exporter sends the traces to OpsRamp cloud and then to the storage to store the data.
Follow the steps below to find out the details about trace collection:
Log in to OpsRamp Portal.
Navigate to Infrastructure > Traces.
On the Traces Configuration page, click LET’S GET STARTED.
You can also access the Traces Configuration from the Menu icon on the left side of this page.Follow the instructions to configure trace proxy under Configure Trace Proxy section.
The trace proxy is configured.