Trace/Span in JSON Logs not capturing in open telemetry collector #5133
kamaldkannan
started this conversation in
General
Replies: 1 comment
-
I think this might something related to instrumentation not including the Span ID / Trace ID. I just did a quick test with opentelemetry-java using log emitter directly, i.e.
And the output in the collector was:
Could you provide more details on the instrumentation setup? Also, I think this question might be more fit for opentelemetry-java |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Please help to advise why Trace/Span in JSON Logs are not capturing in open telemetry collector
Log Published
{"@timestamp":"2022-03-31T18:55:01.290+00:00","severity":"INFO","service":"test","traceId":"f61e7a3e224cc5dc","spanId":"70aa4d30d3b3dba9","pid":"27060","thread":"thread1","class":"c.c.c.t.p.k.f.FunctionConfiguration","messsage":"valid message received"}
Collector Log
Resource SchemaURL: https://opentelemetry.io/schemas/1.8.0
Resource labels:
-> host.arch: STRING(amd64)
-> host.name: ***
-> os.description: ****
-> os.type: STRING(windows)
-> process.command_line: ******
-> process.executable.path: ***
-> process.pid: ***
-> process.runtime.description: ***
-> process.runtime.name: STRING(Java(TM) SE Runtime Environment)
-> process.runtime.version: STRING(11.0.10+8-LTS-162)
-> service.appid: STRING(175828)
-> service.name: ***
-> telemetry.auto.version: STRING(1.11.0)
-> telemetry.sdk.language: STRING(java)
-> telemetry.sdk.name: STRING(opentelemetry)
-> telemetry.sdk.version: STRING(1.11.0)
InstrumentationLibraryLogs #0
InstrumentationLibraryLogs SchemaURL:
InstrumentationLibrary ****
LogRecord #0
Timestamp: 2022-03-31 18:55:01.29 +0000 UTC
Severity: INFO
ShortName:
Body: valid message received
Trace ID:
Span ID:
Flags: 0
Collector config
otel-collector-config: |
receivers:
otlp:
protocols:
grpc:
http:
processors:
batch:
memory_limiter:
# 80% of maximum memory up to 2G
limit_mib: 1500
# 25% of limit up to 2G
spike_limit_mib: 512
check_interval: 5s
exporters:
logs/1:
receivers: [otlp]
processors: [batch]
exporters: [logging]
Beta Was this translation helpful? Give feedback.
All reactions