Replies: 1 comment
-
|
See: #17030 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm exporting metrics to cloudwatch and want the namespace of the containers/services/pods to be visible as a
Dimension. But currently this is not working because theawsemfexporter forces me to configure aNamespacewhich seems to overwrite the Namespace which is available from theawscontainerinsightreceiver(see here: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/awscontainerinsightreceiver )In Cloudwatchlogs I can see that there is the correct Namespace but the metric is pushed with the namespace I have to configure for for the
awsemfexporter.This is my current configuration:
As you might see I've tried to set a new namespace field which I would be able to use with a
processorbut this seems not to be working too. In Clloudwatch logs it always looks like this.{ "ClusterName": "eks-dev", "Namespace": "loki", "NodeName": "ip-10-1-79-141.eu-central-1.compute.internal", "Service": "loki", "Sources": [ "apiserver" ], "Timestamp": "1670489791032", "Type": "ClusterService", "Version": "0", "_aws": { "CloudWatchMetrics": [ { "Namespace": "ContainerInsights", "Dimensions": [ [ "ClusterName", "Namespace", "Service" ], [ "ClusterName" ] ], "Metrics": [ { "Name": "service_number_of_running_pods", "Unit": "Count" } ] } ], "Timestamp": 1670489791032 }, "foo": "bar", "kubernetes": "{\"namespace_name\":\"loki\",\"service_name\":\"loki\"}", "service_number_of_running_pods": 1 }For the moment I'm stuck and I would appreciate any help with this issue. I don't understand why there is a
namespaceparameter for theawsemfexporter. If not set it just writesdefaultin the namespace field. So I need a possibility to use the real namespace.Beta Was this translation helpful? Give feedback.
All reactions