lorelei-rupp-imprivata

> Hi! > > Any progress on this proposal ? you can already implement the things above FYI, there is support to make argo least priv today its just not...

We are seeing this too. Using the PodName dimension but its an aggregate not individual pods. I would expect it to be individual pods given its dimension name is PodName

We tried enabling ``` receivers: awscontainerinsightreceiver: add_full_pod_name_metric_label: true prefer_full_pod_name: true ``` It seemed to get a little better, some pods come through, like stateful sets it seems, but things that...

Any update on this?

Sure, sorry I should have provided more originally This is my full Config Map ```receivers: prometheus: config: global: scrape_interval: 1m scrape_timeout: 10s scrape_configs: - job_name: 'kube-state-metrics' static_configs: - targets: [...

even switching to use ``` - job_name: 'cluster-autoscaler-target' static_configs: - targets: [ 'cluster-autoscaler-aws-cluster-autoscaler.kube-system.svc.cluster.local:8085' ] ``` They still do not show up in the log group in AWS Cloud Watch It...

> If you enable the `logging` exporter does the `cluster_autoscaler_cluster_safe_to_autoscale` metric appear in the logs? Or, if you add a `prometheus` exporter to the pipeline does that metric appear in...

Oh I was missing the logging in the pipeline exporters. I just enabled this and now there is a lot of logs in the pod logs for the collector. I...

It also only has 1 data point. Compared to metrics I do see make it to Cloud Watch logs have multiple data points ``` Metric #41 Descriptor: -> Name: cluster_autoscaler_nodes_count...

> That's good, it tells us the `prometheus` receiver is handling this metric correctly. Having a single datapoint is expected as each unique combination of labels and label values is...