Remove OTEL_GRPC_ENDPOINT and OTEL_SERVICE_NAME if you aren't using OpenTelemetry.įor more information about the parameters, see the Parameters table.AUDIENCE - For ingesting metrics to Azure Monitor Workspace, set AUDIENCE to.AAD_CLIENT_ID - The clientId of the managed identity used that was assigned the Monitoring Metrics Publisher role.To send data to an Azure Monitor workspace, use the hostname part of the Metrics ingestion endpoint from the workspaces Overview page. TARGET_HOST - The target host where you want to forward the request to.Use the following YAML file to deploy the proxy for remote write. scope /subscriptions/ef0123-1243-abcd-9876-1234abcd5678/resourceGroups/MA_amw-proxytest_eastus_managed/providers/Microsoft.Insights/dataCollectionRules/amw-proxytest Select the Data collection rule on the workspace Overview tab, then select JSON view to see the Resource ID.Īssign the Monitoring Metrics Publisher role to the managed identity's clientId so that it can write to the Azure Monitor workspace data collection rule. Use the following command to find the data collection rule ID: az monitor data-collection rule show -name -resource-group -query "id"Īlternatively you can find your DCR ID and Metrics ingestion endpoint using the Azure portal on the Azure Monitor workspace Overview page. The resource group name for your data collection rule follows the format: MA_managed, for example MA_amw-proxytest_eastus_managed. The rule name is same as the workspace name. ![]() "resourceId": "/subscriptions/def0123-1243-abcd-9876-1234abcd5678/resourcegroups/MC_rg-proxytest-01_proxytest-01_eastus/providers/Microsoft.ManagedIdentity/userAssignedIdentities/proxytest-01-agentpool"įind your Azure Monitor workspace's data collection rule (DCR) ID. # Get the identity client_idĪz aks show -g -n -query "identityProfile" The managed identity is created when the AKS cluster is created. ![]() The managed identity is used to authenticate to the Azure Monitor workspace. Prometheus remote write has a dedicated side car for remote writing which is the recommended method for implementing remote write.īefore deploying the proxy, find your managed identity and assign it the Monitoring Metrics Publisher role for the Azure Monitor workspace's data collection rule.įind the clientId for the managed identity for your AKS cluster. This example shows how to use the proxy to authenticate requests for remote write to an Azure Monitor managed service for Prometheus.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |