[beats] add milliseconds to awscloudwatch Filebeat input #43481

[sptsway]

• add milliseconds to awscloudwatch Filebeat input Add milliseconds to awscloudwatch Filebeat input #43481
• time.Unix() takes nanoseconds as second param, the PR converts milliseconds into nanoseconds to fix the issue
• Add milliseconds to awscloudwatch Filebeat input #43481

Proposed commit message

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

How to test this PR locally

Related issues

• Add milliseconds to awscloudwatch Filebeat input #43481

Use cases

Screenshots

Logs

[mergify]

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @sptsway? 🙏.
For such, you'll need to label your PR with:

• The upcoming major version of the Elastic Stack
• The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[elasticmachine]

Pinging @elastic/obs-ds-hosted-services (Team:obs-ds-hosted-services)

[kaiyan-sheng]

Thanks for the fix! Could you add a changelog entry here please? Thank you!

[sptsway]

Thanks for the fix! Could you add a changelog entry here please? Thank you!

does it need to be in the same PR?
edit: nvm done

[Kavindu-Dodan]

changes looks fine. I will wait for #44306 (comment) to be addressed and then we can merge.

@kaiyan-sheng given this is a new addition, we can avoid backports. But let me know your thoughts on that.

[sptsway]

buildkite/beatsExpected — Waiting for status to be reported

@Kavindu-Dodan has this build timedout or something? i dont see option to merge so

[Kavindu-Dodan]

buildkite/beatsExpected — Waiting for status to be reported

@Kavindu-Dodan has this build timedout or something? i dont see option to merge so

buildkite build did not start, I have manually triggered a build based on your change. I will take care of the merge once build is green :)

[sptsway]

buildkite/beatsExpected — Waiting for status to be reported

@Kavindu-Dodan has this build timedout or something? i dont see option to merge so

buildkite build did not start, I have manually triggered a build based on your change. I will take care of the merge once build is green :)

thanks

[Kavindu-Dodan]

There are some integration test failures but they are not related to this change. I will wait till the main branch get stable and rebase this PR.

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b timestamp upstream/timestamp
git merge upstream/main
git push upstream timestamp

[Kavindu-Dodan]

Unfortunately, main branch builds are still failing due to integration test failure. These are tracked with,

• [Flaky Test] filebeat/input/redis TestInput #44247
• The auditbeat file integrity EBPF backend is failing #44174

Will track and re-trigger a build once these are fixed

[sptsway]

hey @Kavindu-Dodan, are the tests fixed and passing now?

[kaiyan-sheng]

/test

[Kavindu-Dodan]

@sptsway builds are green and thank you for the contribution :) I will merge this now and it will be available with 8.19.0 release