Manual Integration of Azure Monitor

this document provides a step by step manual approach to integrating azure monitor with kloudmate using the opentelemetry receiver the azure monitor opentelemetry receiver allows 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 enable service principal azure install the opentelemetry collector on a server where it will scrape the azure monitor metrics and forward them to kloudmate installing the opentelemetry collector step 1 set up the azure monitor receiver in the opentelemetry configuration file linux users open the file located at /etc/otelcol contrib/config yaml /etc/otelcol contrib/config yaml using your preferred text editor windows users create a new file called config yaml config yaml in the c \program files\opentelemetry collector c \program files\opentelemetry collector folder you can use notepad or any text editor to do this 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\ configure the processor section and the kloudmate backend exporter in the opentelemetry configuration file, while defining 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 to restart and verify the status of the opentelemetry (otel) collector, follow these steps for linux execute the following commands sudo systemctl restart otelcol contrib sudo systemctl status otelcol contrib these commands will restart the otel collector 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 " opentelemetry collector " service right click the service and select " restart " after the opentelemetry collector starts, it will scrape metrics from azure monitor and forward them to kloudmate