k8sobjects receiver observed timestamp is missing

[nicolastakashi]

Component(s)

receiver/k8sobjects

What happened?

Description

Currently, the k8sobjects receiver is not setting the observed timestamp to the produced logs, and some platforms may not ingest data since the timestamp and observed timestamp are not present.

Steps to Reproduce

Configure the collector with the k8sobjects receiver.

Expected Result

Have the observed timestamp present on the log entry.

Actual Result

Log entry doesn't have value on the observed timestamp field.

Collector version

v0.71.0

Environment information

Environment

OS: Ubuntu 20.04
Kubernetes: 1.23
Compiler(if manually compiled): N/A

OpenTelemetry Collector configuration

receivers:
  k8sobjects:
    objects:
      - name: events
        mode: watch

processors:
  batch:

exporters:
  logging:
    verbosity: detailed

service:
  pipelines:
    logs:
      receivers:
      - k8sobjects
      processors: 
      - batch
      exporters:
      - logging

Log output

ObservedTimestamp: 1970-01-01 00:00:00 +0000 UTC
Timestamp: 1970-01-01 00:00:00 +0000 UTC
SeverityText:
SeverityNumber: Unspecified(0)
Body: Map({"object":{"apiVersion":"v1","count":25,"eventTime":null,"firstTimestamp":"2023-02-15T16:40:46Z","involvedObject":{"apiVersion":"v1","fieldPath":"spec.containers{container-name}","kind":"Pod","name":"container-container-name-7785f7966-5f2l9","namespace":"default","resourceVersion":"405467798","uid":"a663352f-a300-4c9c-a5da-67b2c196894f"},"kind":"Event","lastTimestamp":"2023-02-15T16:45:36Z","message":"Back-off restarting failed container","metadata":{"creationTimestamp":"2023-02-15T16:40:46Z","managedFields":[{"apiVersion":"v1","fieldsType":"FieldsV1","fieldsV1":{"f:count":{},"f:firstTimestamp":{},"f:involvedObject":{},"f:lastTimestamp":{},"f:message":{},"f:reason":{},"f:source":{"f:component":{},"f:host":{}},"f:type":{}},"manager":"kubelet","operation":"Update","time":"2023-02-15T16:40:46Z"}],"name":"container-container-name-7785f7966-5f2l9.17440cfe2470cf14","namespace":"default","resourceVersion":"66079426","uid":"541a75a2-a3c3-4e17-b1c0-04bf6a05a92c"},"reason":"BackOff","reportingComponent":"","reportingInstance":"","source":{"component":"kubelet","host":"ip.eu-west-1.compute.internal"},"type":"Warning"},"type":"MODIFIED"})
Attributes:
     -> k8s.resource.name: Str(events)
     -> event.domain: Str(k8s)
     -> event.name: Str(container-container-name-7785f7966-5f2l9.17440cfe2470cf14)
Trace ID:
Span ID:
Flags: 0
	{"kind": "exporter", "data_type": "logs", "name": "logging"}

### Additional context

Given the [Otel specification](https://opentelemetry.io/docs/reference/specification/logs/data-model) the `ObservedTimestamp` field SHOULD be set once the event is observed by OpenTelemetry, in case of external events collected by the collector this is the time when OpenTelemetry’s code observed the event measured by the clock of the OpenTelemetry code.

[github-actions]

Pinging code owners:

• receiver/k8sobjects: @dmitryax @harshit-splunk

See Adding Labels via Comments if you do not have permissions to add labels yourself.