Skip to content

Is there a way to close request traces export in provider? #30

Description

@langker

I read the following website to use hertz with opentelemetry:
https://www.cloudwego.io/zh/docs/hertz/tutorials/observability/open-telemetry/

when I run the demo below in my local:
https://github.com/cloudwego/hertz-examples/blob/main/opentelemetry/hertz/server/main.go

Each time I request the server, I found there will always be a error like below:
2023/11/30 10:43:58 traces export: context deadline exceeded: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:4317: connect: connection refused"

In my case, I just need a trace_id and span_id to generate, but not care about whether request traces export in provider, so is there a way to close it?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions