Ability to reference a field from actual beat/metricbeat event inside a beat/metricbeat module configuration

[alaa-mallah]

Describe the enhancement: Ability to reference a field from actual beat event inside a beat module configuration

Describe a specific use case for the enhancement or feature:

Ability to reference the cloud.region field from the metricbeat aws event inside the aws module configuration For example instead of defining the region as us-east-1, have the module to pull it from the event {{cloud.region}}

• module: aws period: 300s credential_profile_name: test-mb metricsets:
  • cloudwatch regions:
  • us-east-1 metrics:
  • namespace: AWS/EC2 name: ["CPUUtilization"] dimensions:
    • name: InstanceId value: i-0686946e22cf9494a

Hoping to be able to do something like this

regions:

• ${cloud.region}

Where cloud.region is coming from the cloud metadata

[elasticmachine]

Pinging @elastic/integrations (Team:Integrations)

[botelastic[bot]]

Hi! We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[alaa-mallah]

Much appreciated looking into this feature request :)

[botelastic[bot]]

Hi! We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!