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.

Sign up for GitHub

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

Jump to bottom

[AWS] event.dataset is not correct if data_stream.dataset is set to a customized value #8810

Closed
kaiyan-sheng opened this issue Dec 28, 2023 · 0 comments · Fixed by #8811
Closed

[AWS] event.dataset is not correct if data_stream.dataset is set to a customized value #8810

kaiyan-sheng opened this issue Dec 28, 2023 · 0 comments · Fixed by #8811
Labels
Integration:aws AWS

Comments

@kaiyan-sheng
Copy link
Contributor

Similar to #7654 we are seeing the same issue in the AWS integration. When user customizes the dataset name when installing integration, event.dataset is wrong. Then event ingestion will fail with error:

"2023-12-18T06:57:54.078Z" [constant_keyword] field [event.dataset] only accepts values that are equal to the value defined in the mappings [aws.cloudwatch_logs], but got [foo]\"}}, dropping event!

This field should be added by the agent so we should remove hardcoded value for event.dataset in all integrations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Integration:aws AWS
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[aws] Remove hardcoded event.dataset field and use ECS field instead kaiyan-sheng/integrations
1 participant
@kaiyan-sheng