Manual Integration of Azure Monitor

this document provides a step by step manual approach to integrating azure monitor with kloudmate using kloudmate agents the kloudmate agents allow you to scrape telemetry data from azure monitor resources and send them to kloudmate for centralized monitoring and analysis pre requisite azure service principal for authentication you will need a service principal with appropriate permissions to access azure monitor apis required settings for authentication subscription id tenant id client id client secret to enable authentication follow the document https //docs kloudmate com/enable service principal azure kloudmate agent installed on the server scraping azure monitor metrics (see agent installation for docid 4wisf1tqcgkdc1gx8irdl and docid\ mohhpc2tz vqaekq9mogq ) step 1 access agents and opentelemetry collector configuration navigate to the kloudmate platform and log in to your account go to settings > agents section here you can view all installed agents access configuration settings for each agent review the default configurations provided by kloudmate to edit an agent's collector configuration select the desired agent click the actions menu (or agent action tab) choose collector configuration a text editor ui will open, allowing you to edit the agent’s yaml configuration directly within the platform 1\ in this configuration file, ensure the azure monitor receiver is set up to collect and send metrics extensions health check pprof endpoint 0 0 0 0 1777 zpages endpoint 0 0 0 0 55679 receivers otlp protocols grpc endpoint 0 0 0 0 4317 http endpoint 0 0 0 0 4318 azuremonitor \# add the correct credentials as per service principal subscription id "\<subscription id>" tenant id "\<tenant id>" client id "\<client id>" client secret "\<client secret>" cloud azurecloud collection interval 60s initial delay 1s \# uncomment and configure to monitor specific resource groups or services \# resource groups \[] \# services \[] to monitor a specific service or resource group, the user can uncomment the resourcegroup\[] resourcegroup\[] and services\[] services\[] entries in the configuration file 2\ set up the exporter as the kloudmate backend by specifying the endpoint and authorisation key in the agent configuration file, and configure the pipeline processors batch send batch size 10000 timeout 30s exporters debug verbosity detailed otlphttp endpoint 'https //otel kloudmate com 4318' headers authorization xxxxx # replace with your actual kloudmate authentication key service pipelines metrics receivers \[otlp, azuremonitor] processors \[batch] exporters \[debug, otlphttp] extensions \[health check, pprof, zpages] step 2 step 4 save configuration and restart agent after updating the configuration, click “ save configuration ” in the ui or, from your server’s console, run for linux execute the following commands systemctl restart kmagent systemctl status kmagent these commands will restart the kloudmate agent and display its current status for windows open the services window press win + r , type services msc , and press ok alternatively, search for " services " in the windows start menu in the services window, locate the " kloudmate agent " service right click the service and select " restart " subsequently, monitor the metrics on the kloudmate dashboard and set up an alarm to receive notifications if the potential metrics for a specific application rise