https://signoz.io logo
#support
Title
# support
s

Saad Ansari

11/21/2023, 6:42 AM
hi team, we're unable to extract trace_id, span_id from the logs body of our node app. We found this issue : https://github.com/SigNoz/signoz/issues/2972#issuecomment-1605923997, similar to our use-case. This is our otelCollectors Config:
Copy code
otelCollector:
  nodeSelector: {<http://karpenter.sh/capacity-type|karpenter.sh/capacity-type>: spot}
  tolerations:
    - key: "<http://gajigesa.com/spot|gajigesa.com/spot>"
      operator: "Equal"
      value: "true"
      effect: "NoSchedule"
  config:
    processors:
      # default parsing of logs
      logstransform/internal:
        operators:
        - type: trace_parser
          trace_id:
            parse_from: attributes.trace_id
          span_id:
            parse_from: attributes.span_id
          trace_flags:
            parse_from: attributes.trace_flags
But still we're unable to see the id's exported as attributes. need help in understanding where exactly we need to add the trace_parser. We also tried adding it under k8s-infra.presets.logsCollection.operators , but that didnt work as well.
image.png
@Kashyap Rajendra Kathrani ^
@nitya-signoz @Chitransh Gupta @Vishal Sharma can you please help us on this issue.
n

nitya-signoz

11/21/2023, 4:08 PM
s

Saad Ansari

11/21/2023, 4:59 PM
tried the above - but no luck @nitya-signoz
n

nitya-signoz

11/21/2023, 5:35 PM
Did you add the processor to the services ?
Copy code
service:
      pipelines:
        logs:
          receivers: [otlp, httplogreceiver/heroku, httplogreceiver/json]
          processors: [logstransform/internal, batch]
          exporters: [clickhouselogsexporter]
s

Saad Ansari

11/22/2023, 5:41 AM
after adding it to the services - its working now.
thanks @nitya-signoz
can you also point me to the docs where it says we should add it to the services ?
n

nitya-signoz

11/22/2023, 5:46 AM