Go OpenTelemetry Auto-Instrumentation

OpenTelemetry Go instrumentation gives you the ability to capture telemetry (metrics and traces) data from code written in Go. The best way is to use OpenTelemetry-Go. See the list of supported libraries.

Automatic instrumentation

The best way to use Go instrumentation is to include a supported library in your code. See below for steps required to instrument the application automatically.

The instructions below apply to version v1.30.0 (sdk) and 0.55.0 (instrumentation) of OpenTelemetry.

Mandatory packages installation

Installation of packages listed below is mandatory to start working with instrumentation:

go get -u go.opentelemetry.io/otel@v1.30.0
go get -u go.opentelemetry.io/otel/sdk@v1.30.0

It downloads and installs OpenTelemetry package for Go. It includes APIs for traces.

Next, you'll install the spans exporter. There are currently three supported protocols OTLP, Zipkin and Jaeger. Sumo Logic recommends the OTLP HTTP exporter. Execute the command below:

go get -u go.opentelemetry.io/otel/exporters/otlp/otlptrace@v1.30.0
go get -u go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp@v1.30.0

Application specific packages installation

Next, we need to download instrumented versions of libraries and put them into the following path:

go.opentelemetry.io/contrib/instrumentation/{IMPORT_PATH}/otel{PACKAGE_NAME}@{VERSION}

For example, net/http package, which will be used in the example HTTP client code below:

go get go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp@v0.55.0

Import and initialize instrumentation packages 

To get traces from your application, you need to import instrumented libraries and initialize them. An example of an HTTP client-server app using an instrumented library can be found here.

Tracing initialization requires a few steps to be ready. The first one is to configure the OTLP HTTP exporter client. The next step is to set up a Batch Span Processor responsible for batching spans and then TracerProvider. For configuration details, see TracerProvider implementation. Last part of the code is responsible for trace context propagation.

func initTracer() {

    ctx := context.Background()

    client := otlptracehttp.NewClient()

    otlpTraceExporter, err := otlptrace.New(ctx, client)
    if err != nil {
        log.Fatal(err)
    }

    batchSpanProcessor := trace.NewBatchSpanProcessor(otlpTraceExporter)

    tracerProvider := trace.NewTracerProvider(
        trace.WithSpanProcessor(batchSpanProcessor),
        //trace.WithSampler(sdktrace.AlwaysSample()), - please check TracerProvider.WithSampler() implementation for details.
    )

    otel.SetTracerProvider(tracerProvider)
    otel.SetTextMapPropagator(propagation.NewCompositeTextMapPropagator(
        propagation.TraceContext{}, propagation.Baggage{}))
}

After preparing the tracing initialization code, use the initTracer() method and instrumented library. See the following example HTTP client main function:

func main() {

    initTracer()

    client := http.Client{Transport: otelhttp.NewTransport(http.DefaultTransport)}

    ctx := baggage.ContextWithoutBaggage(context.Background())

    req, _ := http.NewRequestWithContext(ctx, "GET", "http://sumologic.com", nil)

    fmt.Printf("Sending request...\n")
    res, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    fmt.Printf("Response status code: %v\n", res.Status)
    fmt.Printf("Waiting for few seconds to export spans ...\n\n")
    time.Sleep(10 * time.Second)
}

The last step is to configure few other things like:

• SERVICE_NAME. Insert the application service name. Ensure the string value represents its business logic, such as "SumoWebCall". This will appear as a tracing service name in Sumo Logic.
• APPLICATION_NAME. Insert the application name. This will appear as a tracing application name in Sumo Logic. Additional attributes can be added here as comma separated key=value pairs. For example, add the deployment.environment=[environment-name] tag as needed to allow for filtering by environment on dashboard panels (for more information, see Services Dashboard Panels).
• ENDPOINT_ADDRESS. OTLP HTTP (default port 4318) endpoint address must be provided with the location of the OpenTelemetry Collector/Agent (recommended for production) or OTLP/HTTP source. Refer to the following setup instructions if you haven't yet installed a collector:
  • Set up traces collection for Kubernetes environments
  • Set up traces collection for other environments usage

All of them can be configured by environment variables specific for the exporter. For OTLP HTTP Exporter these are:

export OTEL_EXPORTER_OTLP_ENDPOINT="ENDPOINT_ADDRESS"
export OTEL_SERVICE_NAME="SERVICE_NAME"
export OTEL_RESOURCE_ATTRIBUTES="application=APPLICATION_NAME,deployment.environment=ENVIRONMENT_NAME"

Manual instrumentation

If you’re using libraries that are not officially supported, or if you want to be very specific and granular with instrumentation, you can instrument your code manually using https://pkg.go.dev/go.opentelemetry.io/otel/api. Examples of using manual instrumentation can be found here