-
Notifications
You must be signed in to change notification settings - Fork 71
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
Ops Agent does not support traceSampled field mapping #1700
Comments
Hi @PawelKGalka, Can you try doing |
hi @braydonk We were facing similar issue with map_values:
"true" : true
"false": false |
Hi @PawelKGalka, just to learn a bit more about your use case, would it be acceptable if the Ops Agent were to set We've had a few other folks ask for ability to set |
Hi @jefferbrecht, Our application is utilizing tracing in 3 modes based on particular criterias - DROP,RECORD,RECORD_AND_SAMPLE (from OTEL lib). This means there are cases where we trace to correlate transaction in the logs but we do not sample it to Cloud Trace. So for our use case it would be best to have this configurable in the config. Or it can take precedence over default setting when spanId/traceId is set |
This issue was marked stale due to lack of activity. It will be closed in 14 days. |
Describe the bug
When trying to set
jsonPayload."logging.googleapis.com/trace_sampled"
it is not displayed as mapped in Logs Explorer and remains in jsonPayloadTo Reproduce
Steps to reproduce the behavior:
and restart the agent
6. See log entry does not have
traceSampled
property and it remains in jsonPayload asjsonPayload."logging.googleapis.com/trace_sampled": "false"
Expected behavior
Value mapped in logs explorer
Environment (please complete the following information):
Additional context
NA
The text was updated successfully, but these errors were encountered: