https://cerbos.dev logo
#help
Title
# help
r

Rasmus Dencker

06/02/2022, 4:35 PM
After enabling tracing I'm getting this error:
{"log.level":"warn","@timestamp":"2022-06-02T16:23:26.596Z","log.logger":"cerbos.otel","message":"OpenTelemetry error","error":"starting span \"ExportMetrics\": unsupported sampler: 0x7df690"}
- any clue?
e

Emre (Cerbos)

06/02/2022, 7:24 PM
Hi Rasmus, I am not sure. However, perhaps @Charith (Cerbos) or @Dennis (Cerbos) can help.
c

Charith (Cerbos)

06/02/2022, 7:29 PM
It's an annoying but harmless issue in the OpenTelemetry library. I haven't found a solution for it yet. You can safely ignore that log message.
r

Rasmus Dencker

06/02/2022, 7:50 PM
Oh, right. Thanks @Charith (Cerbos). I wasn't seeing any traces in Tempo, so I was wondering if it was related. I'll dig further 😄
got it working!
c

Charith (Cerbos)

06/02/2022, 8:02 PM
Excellent! We have only tested with Jaeger. Did you have to do anything special to send traces to Tempo?
r

Rasmus Dencker

06/02/2022, 8:06 PM
Nope. Tempo supports a bunch of different formats, including Jager
message has been deleted
That's all I had do to. Identical to Jaeger, but it's ingested in Tempo
message has been deleted
c

Charith (Cerbos)

06/02/2022, 8:07 PM
Cool!
❄️ 3
21 Views