[Functionbeat] fix cloudwatch logs timestamp to use logRecord timestamp…

[sbasgall]

… instead of record processing timestamp

The suggested TODO code passes the Cloudwatch timestamp as seconds. The Cloudwatch field value is milliseconds. Pass it as nanoseconds times 1000000.

Closes: #12412

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[sbasgall]

When I run mage fmt update as suggested by the CI I get an error

If I run it from the root of the repo: I see unknown target specified: update
If I run it from the x-pack/functionbeat directory: I see Unknown target specified: fmt

I'm happy to make any changes needed but could use some guidance.

Thank you!

[kaiyan-sheng]

For your question about mage, maybe run mage fmt under x-pack/functionbeat 😬

[sbasgall]

@kaiyan-sheng Thank you! I was able to just run mage fmt from the root of the whole repo and it fixed my formatting error.

[sbasgall]

Should I not be using master branch in my forked source branch?

[ph]

@sbasgall Fixes look good to me, can we add a simple test in https://github.com/elastic/beats/blob/master/x-pack/functionbeat/provider/aws/aws/transformer/transformer_test.go to make sure we never have a regression on it.

[kvch]

jenkins test this

[ph]

@kvch I think we can merge this as is and we can add a test in the #13317 PR

[kvch]

Thank you!

[sbasgall]

Thank you all so much, Last week we were in the final stages of our migration to Elastic and I was unable to find any quiet time to write the tests.