Skip to content

trace_id field extraction from logs #223

@ghost

Description

Dear Team,
We have installed Signoz using helm charts by supplying override-values.yaml in our EKS cluster. After installation -we configured OTEL URL in our apps.

In the Frontend dashboard, we were able to see logs coming in but we were not getting value for trace_id field. I have attached the screenshot where traced_id is showing body{} but not coming in the interested fields.

Can someone please help here with what could be the issue? I have attached my override-values.yaml and screenshot missing trace_id from logs

override-values.yaml :

global:
storageClass: gp2
cloud: gcp

clickhouse:
installCustomStorageClass: true
otel:
receiver:
otlp:
protocols:
grpc:
endpoint: otel-collector.default.svc.cluster.local:4317
exporter:
jaeger:
endpoint: http://jaeger-query:16686
logging:
loglevel: debug
logformat: json
processor:
batch:
timeout: 5s
attribute:
actions:
- key: trace_id
action: upsert
from_attribute: log
value_type: string
otlp:
protocols:
grpc:
parser:
json:
timestamp:
field: "time"
format: "RFC3339Nano"
attributes:
- key: log
field: "message"
- key: trace_id
field: "trace_id"

signoz

Metadata

Metadata

Assignees

Labels

chart:k8s-infraIssue related to k8s-infra helm chartenhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions