Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Functionbeat] Kinesis timestamp ignored #33095

Closed
adrian-skybaker opened this issue Sep 15, 2022 · 0 comments · Fixed by #33593
Closed

[Functionbeat] Kinesis timestamp ignored #33095

adrian-skybaker opened this issue Sep 15, 2022 · 0 comments · Fixed by #33593
Labels
Team:Cloud-Monitoring Label for the Cloud Monitoring team

Comments

@adrian-skybaker
Copy link

Similar to #12412, the kinesis source ignores the timestamp in the record and uses time.Now():

		for _, deaggRecord := range deaggRecords {
			beatEvents = append(beatEvents, beat.Event{
				Timestamp: time.Now(),

This is at odds with the documentation at https://www.elastic.co/guide/en/beats/functionbeat/current/exported-fields-ecs.html:

@timestamp
Date/time when the event originated. This is the date/time extracted from the event, typically representing when the event was generated by the source. If the event source has no original timestamp, this value is typically populated by the first time the event was received by the pipeline.

@adrian-skybaker adrian-skybaker changed the title Kinesis timestamp ignored [Functionbeat] Kinesis timestamp ignored Sep 15, 2022
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Sep 15, 2022
@endorama endorama added the Team:Cloud-Monitoring Label for the Cloud Monitoring team label Sep 19, 2022
@botelastic botelastic bot removed the needs_team Indicates that the issue/PR needs a Team:* label label Sep 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Cloud-Monitoring Label for the Cloud Monitoring team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants