#support

Troubleshooting Missing Operation Name in Instrumentation

TLDR Sanjiv added code to match service name from automatic instrumentation, but operation name was missing. User resolved the issue, suggesting improvement in documentation.

9mo

Join the chat

Feb 28, 2023 (9 months ago)

Photo of md5-914a8b39b82fd99b8ecd985427660deb

Sanjiv

09:02 PM

I added the following code but where “my-service-name” matches the service name from the automatic instrumentation and what appears in SigNoz. However the operation “my-operation-name” never appears anywhere.

        Tracer tracer = GlobalOpenTelemetry.getTracer("my-service-name");

        Span childSpan = tracer.spanBuilder("my-operation-name").setSpanKind(SpanKind.SERVER).startSpan();
        childSpan.setAttribute("foo", "bar");

Mar 01, 2023 (9 months ago)

Sanjiv

01:09 AM

I was able to figure this out with a fair amount of difficulty. The docs in this area should be improved

SigNoz Community

Built with ClickHouse as datastore, SigNoz is an open-source APM to help you find issues in your deployed applications & solve them quickly | Knowledge Base powered by Struct.AI

Indexed 1023 threads (61% resolved)

Join Our Community

Similar Threads

Changing OperationName for Request in .Net for SigNoz

Ognen asked about changing the operation name in .Net for SigNoz. Prashant suggested using 'StartActiveSpan' and 'UpdateName' functions through manual instrumentation.

7mo

Filling in Method for Traces in Go Instrumentation

Timothy asked about filling in the method for traces in Go. vishal-signoz identified a workaround by changing the spankind to Internal, and shared a PR for the fix.

9mo

Customizing Signoz Error Alert Descriptions

Sumanth needed help with making Signoz error alert descriptions more descriptive. Amol suggested using {{.Labels.serviceName}} and discussed limitations of adding labels in queries.

5mo