k8seventsreceiver milliseconds precision

[aahmadzada-png]

Hi, we are trying to use k8seventsreceiver with the opensearchexporter (ss4o mode) and noticed that Kubernetes events only provide second-precision timestamps.

In metricbeat, @timestamp was set to time.Now() at the moment the Watch callback processed each event. This gave every event a unique millisecond-precision timestamp that preserved the exact Watch stream delivery order — useful for incident investigation when multiple events happen within the same second.

We were hoping observedTimestamp could serve the same purpose in OTel, since it has nanosecond precision. However, we observed cases where observedTimestamp diverges significantly from @timestamp. For example:

@timestamp: 2026-03-18T10:10:00Z
observedTimestamp: 2026-03-18T11:12:17.356340573Z
This is a ~1 hour gap, suggesting the event was re-delivered during a re-list and got a new observedTimestamp on re-ingestion. It is expected?