ory
`persistence.sql.NextMessages` registers as Error in otel-tracing
Preflight checklist
- [X] I could not find a solution in the existing issues, docs, nor discussions.
- [X] I agree to follow this project's Code of Conduct.
- [X] I have read and am following this repository's Contribution Guidelines.
- [X] I have joined the Ory Community Slack.
- [ ] I am signed up to the Ory Security Patch Newsletter.
Ory Network Project
No response
Describe the bug
We sample 100% of errors in our otel setup.
And unfortunately this persistence.sql.NextMessages job that runs constantly registers as error, probably when it cant find any new messages.
But that shouldnt be a error imo.
Reproducing the bug
setup otel tracing, and you will see persistence.sql.NextMessages registers as Error in apm.
Im using signoz as apm.
Relevant log output
No response
Relevant configuration
No response
Version
v1.2.0
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Kubernetes with Helm
Additional Context
No response
We are also facing the same issue with Kratos v1.3.0, Otel collector, and Grafana Tempo.
@afreakk Did you find any solution that you can share for the time being until this gets fixed? Thanks!
In my case, I was using Jaeger v2, but persistence.sql.NextMessages traces—which I considered unnecessary—kept appearing, so I simply filtered them out.
Seeing the same issue when I run locally with Jaeger v1 or v2. It is quite confusing when you a new to Ory as I am when you see a trace with an error that doesn't show up any errors
