inputs.cloudwatch: Error when using multiple namespaces

[atartareanu]

Use Case

Hello
Thank you for making this possible: configure multiple namespaces in telegraf cloudwatch input
#9386

However there is no concrete example how to configure this, especially for the tree of metrics and dimensions. I have tried multiple combinations and some do not make sense, but still work like:

namespaces = ["AWS/Billing", "AWS/ECS"]

[[inputs.cloudwatch.metrics]]
names = ["MemoryUtilization", "CPUUtilization"]
  
[[inputs.cloudwatch.metrics.dimensions]]
name = "ServiceName"
value = "*"

[[inputs.cloudwatch.metrics.dimensions]]
name = "ClusterName"
value = "*"

[[inputs.cloudwatch.metrics]]
names = ["EstimatedCharges"]
  
[[inputs.cloudwatch.metrics.dimensions]]
name = "ServiceName"
value = "*"

[[inputs.cloudwatch.metrics.dimensions]]
name = "Currency"
value = "*"

[[inputs.cloudwatch.metrics]]
names = ["EstimatedCharges"]

[[inputs.cloudwatch.metrics.dimensions]]
name = "Currency"
value = "USD"

so I put AWS/Billing first in the namespaces and AWS/ECS second, but the associated metrics are reversed, however it's the only combination that works, but where is the logic ?

Also when trying to add another namespace, e.g. , "AWS/ApplicationELB" the previous config does not work, I will only get data for a single namespace.

Can you please provide an example of configuration with 3 namespaces + random metrics and dimensions.

Thank you.

Expected behavior

The documentation/config example should contain configuration for multiple namespaces

Actual behavior

there is no logic on how this works. we want to understand and make it better.

Additional info

No response

[powersj]

Hi,

This sounds more like a support request, that would be better asked in Slack or on our community forums.

Can you show your full cloudwatch config as well as logs, please? I ask because you have one "namespace" option that isn't even in the cloudwatch plugin section and it helps to not hide any config options from us if we are trying to support you.

It sounds like you are doing the right thing, but running into actual issues, as such showing your logs would really help us understand what you are seeing, rather than needing to guess.

Let's try with a single namespace and the three metrics:

[[inputs.cloudwatch]]
  <add your auth items>
  <are there any other options outside of auth you are using, if so please let us know>
  namespaces = ["AWS/Billing"]

  [[inputs.cloudwatch.metrics]]
    names = ["MemoryUtilization", "CPUUtilization"]
    [[inputs.cloudwatch.metrics.dimensions]]
      name = "ServiceName"
      value = "*"
    [[inputs.cloudwatch.metrics.dimensions]]
      name = "ClusterName"
      value = "*"

  [[inputs.cloudwatch.metrics]]
    names = ["EstimatedCharges"]
    [[inputs.cloudwatch.metrics.dimensions]]
      name = "ServiceName"
      value = "*"
    [[inputs.cloudwatch.metrics.dimensions]]
      name = "Currency"
      value = "*"

  [[inputs.cloudwatch.metrics]]
    names = ["EstimatedCharges"]
    [[inputs.cloudwatch.metrics.dimensions]]
      name = "Currency"
      value = "USD"

Does that work? If so, great, try the other namespace by itself. Does that work?

If this does not work, can you confirm that you can actually see these metrics using the CLI. Checkout the Troubleshooting section and verify that each of these work for the namespace.

[atartareanu]

Hello @powersj
Thank you for your quick reply, I was not aware we can get support on Slack, I will try my luck there by providing additional information.

[srebhan]

Further digging brought up the error message

[inputs.cloudwatch] failed to list metrics with namespace AWS/ApplicationELB: operation error CloudWatch: ListMetrics, https response error StatusCode: 400, RequestID: [REDACTED], InvalidParameterValue: Parameters do not match original request parameters

occurring during ListMetrics.

[bwesen]

Can't you just replicate the whole inputs.cloudwatch section multiple times, each time with a different namespace? I ran into this now as well, and it's not obvious how to do this but that would be logical..