-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
W3C tracing does not work as expected #6905
Comments
I think you'll have to set |
Hey @ashutosh-narkar, this works, but that also means that it tries to send the traces to an OpenTelemetry Tracing endpoint. We do not have that. So we can not fill in the I've also tried putting the sample_percentage to 0, but then still it tries to send the spans (or at least, create the connection). Maybe an option |
Sure, feel free to submit a PR with the doc updates.
If you turn on console decision logging they get logged. Couldn't you just use that? |
This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. Although currently inactive, the issue could still be considered and actively worked on in the future. More details about the use-case this issue attempts to address, the value provided by completing it or possible solutions to resolve it would help to prioritize the issue. |
Short description
According to the documentation, OPA supports W3C tracing. Thus, we send the
traceparent
header to OPA when performing a REST request that evaluates policies. But we can not find a single place where this trace information is outputted.The documentation regarding decision logs mentions that the log should output the trace_id and span_id. But the trace info is not shown when outputting the decision logs to the console, configured using
decision_logs.console=true
.OPA version used:
0.67.0
Steps To Reproduce
policy/example.rego
with the contentdocker-compose.yml
file with the contentExpected behavior
We expect that (at least) the decision log in console contains the
trace_id
andspan_id
as mentioned in the documentation.It would also be good that every log statement performed in this current span contain the trace_id and span_id.
We do not have a central OpenTelemetry collector that is able to receive requests made using the Decision Log Service API. We do have log collectors running on every pod. So outputting the log in the console is a good option for us.
The text was updated successfully, but these errors were encountered: