Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Metricbeat] Cloudwatch metricset config doesn't work with both name and dimensions #14376

Closed
kaiyan-sheng opened this issue Nov 1, 2019 · 0 comments · Fixed by #14391
Closed
Assignees
Labels
bug Metricbeat Metricbeat Team:Integrations Label for the Integrations team

Comments

@kaiyan-sheng
Copy link
Contributor

With 7.4 Metricbeat, if I run cloudwatch metricset with specified metric names(more than one name) and dimensions, only one specified metric name will be collected. For example, with aws.yml:

- module: aws
  period: 300s
  metricsets:
    - cloudwatch
  credential_profile_name: test-mb
  metrics:
    - namespace: AWS/RDS
      name: ["CPUUtilization", "FreeableMemory"]
      dimensions:
        - name: DBInstanceIdentifier
          value: database-1
      statistic: ["Average", "Maximum"]

Only FreeableMemory metric will be collected but not CPUUtilization for database-1.

Workaround for this is to separate the metric names into two parts of the config:

- module: aws
  period: 300s
  metricsets:
    - cloudwatch
  credential_profile_name: test-mb
  metrics:
    - namespace: AWS/RDS
      name: ["FreeableMemory"]
      dimensions:
        - name: DBInstanceIdentifier
          value: database-1
      statistic: ["Average", "Maximum"]
    - namespace: AWS/RDS
      name: ["CPUUtilization"]
      dimensions:
        - name: DBInstanceIdentifier
          value: database-1
      statistic: ["Average", "Maximum"]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Metricbeat Metricbeat Team:Integrations Label for the Integrations team
Projects
None yet
1 participant