You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have changed the method for configuring logging. Previously, logging configs were managed as Azure DevOps Pipeline variables stored in a yaml (previous example) and passed to ARM via Azure CLI as inline values. Our new path is to migrate all relevant configs to an ARM JSON Parameter file.
Our goal with this change is to simplify the deployment and configuration of logging. This includes easier support for multiple Log Analytics Workspaces and simplifies deployment through PowerShell, Azure CLI, GitHub Actions, etc.
This change is in effect as of April 8, 2022 and will be part of v0.10.0 release (April 2022).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We have changed the method for configuring logging. Previously, logging configs were managed as Azure DevOps Pipeline variables stored in a yaml (previous example) and passed to ARM via Azure CLI as inline values. Our new path is to migrate all relevant configs to an ARM JSON Parameter file.
Our goal with this change is to simplify the deployment and configuration of logging. This includes easier support for multiple Log Analytics Workspaces and simplifies deployment through PowerShell, Azure CLI, GitHub Actions, etc.
This change is in effect as of April 8, 2022 and will be part of v0.10.0 release (April 2022).
Migration instructions
See Migrate Logging configuration from Azure DevOps variables to JSON parameters file in Azure DevOps Pipelines Onboarding Guide for step by step instructions.
Change details
Beta Was this translation helpful? Give feedback.
All reactions