Configuring diagnostic settings for Azure services using bicep

If you’re hosting your application infrastructure in Azure and consolidate the diagnostic and audit information from your services into Log Analytics or elsewhere, it’s pretty easy to do using Bicep. It’s not very well documented, however, which is the reason for this post. A quick description of our problem If we’re building an application using Azure services then it’s important to think about telemetry. In simple terms, we have two sources of telmetry: Our application code should be instrumented to emit telemetry, either using Open Telemetry, or the Application Insights SDK (this isn’t an otel article - whichever works for you); The Azure services also generate metrics, audit data and logging.

For the full version of this post see Rik Hepworth's personal blog at Configuring diagnostic settings for Azure services using bicep