Skip to content

AWS Billing module EstimatedCharges field doesn't match integration #1592

@legoguy1000

Description

@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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions