AWS Billing module EstimatedCharges field doesn't match integration

[legoguy1000]

The Metricbeat AWS Billing module sets the field EstimatedCharges as a Long. The AWS Billing Integration data stream for the agent sets EstimatedCharges.max as a Long. User reported an error with the AWS agent integration https://elasticstack.slack.com/archives/CNTP6NLTZ/p1631079578142800?thread_ts=1631079307.142600&cid=CNTP6NLTZ.

(status=400): {"type":"mapper_parsing_exception","reason":"object mapping for [aws.billing.EstimatedCharges] tried to parse field [EstimatedCharges] as object, but found a concrete value"}

The change in the Metricbeat module from EstimatedCharges.max to EstimatedCharges was made in elastic/beats#20527
The AWS Integration needs to update its field mapping to match the Metricbeat module.

[legoguy1000]

@kaiyan-sheng thoughts?

[kaiyan-sheng]

Yes this is a bug caused by not syncing the change between beats and the integration 👍 Thanks for catching it! Will fix it right away.

[legoguy1000]

I have a branch already, just hadn't pushed it yet. I can push it shortly for u too look at if u want or if there are other changes u want to make as well, I can just toss it.

[kaiyan-sheng]

@legoguy1000 😂 sorry!!! I just saw your comment...!!

[legoguy1000]

@legoguy1000 😂 sorry!!! I just saw your comment...!!

no problem, i figured there were other changes that needed to be made too. Glad it was fixed.

[kaiyan-sheng]

Thank you for creating the issue!!!

[threenub]

Thanks all - as the user that reported it let me know if I can help or test in any way.

[threenub]

Hi @kaiyan-sheng -- how long roughly until this fix makes it into the repo?

[kaiyan-sheng]

@threenub The PR is merged into 0.10.6 version of the AWS package, which is still in staging right now. It will be pushed into production in next day or two.