From ddc9e60a9ec1c4115eafc7adeccce5894e53d1b6 Mon Sep 17 00:00:00 2001 From: Jesper Fajers Date: Mon, 15 Jan 2024 18:11:26 +0000 Subject: [PATCH] Update --- docs/wiki/Monitoring.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/wiki/Monitoring.md b/docs/wiki/Monitoring.md index 6254d1ed..25e5f7a8 100644 --- a/docs/wiki/Monitoring.md +++ b/docs/wiki/Monitoring.md @@ -2,7 +2,8 @@ - [Introduction](#introduction) - [Troubleshooting AzOps](#troubleshooting-azops) -- [External Monitoring](#external-monitoring) +- [Application Insights](#azure-monitor-application-insights) + - [Enable Application Insights Monitoring](#enable-application-insights-monitoring) --- @@ -20,7 +21,7 @@ Depending on the numeric value set for `Message.Info.Maximum` at `settings.json` During normal operations changes to verbosity levels are not needed and the default is sufficient. However, when troubleshooting and trying to understand the why and the what has happened it is advised to increase the verbosity to at least `5` or `8`, going all the way up to `9` makes the module very noisy and the amount of events emitted are high [read more](https://github.com/azure/azops/wiki/troubleshooting). -## External Monitoring +## Azure Monitor Application Insights By design the module emits logs to console during execution, in addition to that the module can emit logs to Azure Monitor Application Insights. @@ -32,7 +33,7 @@ This can be useful to track performance, key metrics, and exceptions over time. It is also helpful when you are running the module with several parallel threads `Core.ThrottleLimit` > `1` due to that console output does not work well when running in parallel. By emitting information to Azure Monitor Application Insights this can be overcome without adjusting the `Core.ThrottleLimit`. -Enable Application Insights monitoring: +### Enable Application Insights Monitoring 1. [Create a Application Insights resource](https://learn.microsoft.com/en-us/azure/azure-monitor/app/create-workspace-resource#create-a-workspace-based-resource). 1. Add a secret named `APPLICATIONINSIGHTS_CONNECTIONSTRING` *(in GitHub or Azure Pipelines)* and enter the connection string for you Application Insights resource, [find your connection string](https://learn.microsoft.com/en-us/azure/azure-monitor/app/sdk-connection-string?tabs=dotnet5#find-your-connection-string).