-
Hi, I could manage to set up the promitor application in kubernetes environment. The application is up and running without any issues. However, it does not scrape metrics from Azure monitor. Here is the configuration for setting up the promitor scraper agent (without resourceDiscovery).
I can see there is some authentication failure logs in the container logs though. Here is the container logs:
Here are the metrics what promitor is exposing now:
What I understood from the container log is, the UserAssignedManagedIdentity authentication is failing when scraping metrics from azure monitor. But, I tried the same UserAssignedManagedIdentity as aadpodidbinding with azure_metrics_exporter and it returns the metrics without any issues. So, wondering if I have done any mistakes in the configurations side? For authentication.identityId in runtime.yaml, I am using the same value what I am using for aadpodidbinding in deployment label section. I believe that is the correct configuration. Please help. Thanks, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
I might be wrong but I believe that has to be the app id instead, but @Mimetis implemented it so he might be able to refresh my memory |
Beta Was this translation helpful? Give feedback.
-
Thanks @tomkerkhove for the response. I tried the same configuration with "Client ID" / "Object (principal) ID" instead of using aadpodidbinding value for authentication.identityId in runtime.yaml. But, still the application is not scraping the metrics from Azure monitor. Since we are using user assigned managed identity, i believe we don't need to create any applications. So, can you please provide some more details about what could be the app id value when we use "user assigned managed identity"? Thanks, |
Beta Was this translation helpful? Give feedback.
-
Any suggestion on this please? |
Beta Was this translation helpful? Give feedback.
Any suggestion on this please?