Open sdejong629 opened 3 months ago
Pinging code owners:
receiver/webhookevent: @atoulme @shalper2
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Hey thanks for the issue! I think that there should be a timestamp set at the log level when the receiver gets an event (PR to follow). I would like to point out though that this value will have a different meaning than the time value in the event's payload.
That's okay, at least this will be an indication of time at least
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Component(s)
receiver/webhookevent
What happened?
Description
We export minio audit logs to an opentelemetry webhook_event_receiver, but no timestamp is set anywhere in the resulting logs. Clickhouse uses the timestamp to calculate the TTL of the log entries. The TTL expires immediately after the log has entered the system
Steps to Reproduce
Expected Result
The expected result would be that a timestamp is set for at least the moment of receiving the event or maybe grab it from the minio logs itself (schema at https://min.io/docs/minio/windows/operations/monitoring/minio-logging.html#audit-log-structure) or some way to point the webhookeventreceiver where to get it's timestamp from.
Actual Result
No timestamp is set for a given log entry. Clickhouse for example therefor removes all logs after the TTL has expired (which is pretty much immediately)
Collector version
0.102.0
Environment information
Environment
Otel client on Ubuntu 22.04 Otel gateway on docker on Ubuntu 22.04
OpenTelemetry Collector configuration
Log output
Additional context
No response