-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
Logging 6.0.0
-
False
-
None
-
False
-
NEW
-
OBSDA-498 - Enable OpenTelemetry in Cluster Logging Operator
-
NEW
-
Bug Fix
-
-
-
Moderate
Description of problem:
Log data in otlp server doesn't contain the attribute `openshift.sequence`:
ResourceLog #0 Resource SchemaURL: Resource attributes: -> cluster.id: Str(18c73958-b766-4214-83bc-710068563f45) -> openshift.log.source: Str(container) -> k8s.pod.name: Str(centos-logtest-qkm49) -> k8s.container.name: Str(centos-logtest-container-0) -> k8s.namespace.name: Str(test) ScopeLogs #0 ScopeLogs SchemaURL: InstrumentationScope LogRecord #0 ObservedTimestamp: 2024-08-15 07:39:06.638842896 +0000 UTC Timestamp: 2024-08-15 07:38:38.623252759 +0000 UTC SeverityText: SeverityNumber: Info(9) Body: Str({"message": "MERGE_JSON_LOG=true", "level": "debug","Layer1": "layer1 0", "layer2": {"name":"Layer2 1", "tips":"Decide by PRESERVE_JSON_LOG"}, "StringNumber":"10", "Number": 10,"foo.bar":"Dot Item","{foobar}":"Brace Item","[foobar]":"Bracket Item", "foo:bar":"Colon Item","foo bar":"Space Item" }) Attributes: -> openshift.log.type: Str(application) -> openshift.label.clf_observability_openshift_io: Str(logging-74947) -> openshift.label.label-test: Str(ocp-74947) -> k8s.pod.uid: Str(6b8fe9cc-6dce-443a-ad1f-29a938f01ab1) -> k8s.container.id: Str(cri-o://4a8942d9c895150d385a372e8884530db6314c7089fe6be510c442aa85168543) -> k8s.pod.label.run: Str(centos-logtest) -> k8s.pod.label.test: Str(centos-logtest) Trace ID: Span ID: Flags: 0
Version-Release number of selected component (if applicable):
openshift-logging/cluster-logging-rhel9-operator/images/v6.0.0-72
How reproducible:
Always
Steps to Reproduce:
- forward logs to otlp output
- check log data
Actual results:
Field `openshift.sequence` is defined in the vector.toml, but it's not added into log data.
Expected results:
The logs received in OTLP server should contain `openshift.sequence`