Ben

I am also receiving BadRequest responses for EventHub, but they are slightly different errors ``` - name: azure_eventhubs_activeconnections_average description: "Total Active Connections for Microsoft.EventHub." resourceType: EventHubs azureMetricConfiguration: metricName: ActiveConnections aggregation:...

I was able to find a workaround to get Workload Identity working by using these helm values: ``` podLabels: azure.workload.identity/use: "true" rbac: serviceAccount: create: false name: workload-identity-sa azureAuthentication: mode: "UserAssignedManagedIdentity"...

I made an assumption that the changes/workaround config would also work for the Scraper. I was testing the Scraper and am now getting different Identity issues. Will spend some time...

It looks to be due to Azure Monitor integration using ``Microsoft.Azure.Management.ResourceManager.Fluent.Authentication`` instead of the Azure SDK/Azure Identity library like Resource Discovery is using. There is a way to get it...

@davecaplinger Here are the labels and annotations I needed to use for the sidecar proxy to work securityContext: runAsNonRoot: false #Required for Azure Workload Identity Proxy Injection podLabels: azure.workload.identity/use: "true"...

We were able to confirm that 120 logical cpu's is fine, but adding 1 more(smt8) to 128 logical cpu's causes the segmentation fault >Can you give https://github.com/grafana/node_exporter_aix/releases/tag/v1.15.6 a whirl? We...

> Can you give https://github.com/grafana/node_exporter_aix/releases/tag/v1.15.6 a whirl? Testing it with some of our users and it solved segmentation fault, would love to see if it also solves your issues. Once...

> https://github.com/grafana/node_exporter_aix/releases/tag/v1.15.7