Azure / Azure/bicep

Add Monitor tab in Deployment Scripts

Open
#17,203 0 comments 0 reactions 0 assignees View on GitHub
Deployment Scripts enhancement Needs: Upvote
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

**Is your feature request related to a problem? Please describe.**
Yes, Deployment Scripts has a feature to show outputs from a run and we would like to use those values to create Alerts.

**Describe the solution you'd like**

Add Monitoring tab, with `Diagnostic Settings` similar to other resources, example below:

![Image](https://github.com/user-attachments/assets/cfe2c3d7-015e-4603-a478-204dfe10adea)

That way we could monitor what is in `Output` tab, that tab is very important for users that add output in scripts to help monitor and debug stuff:

![Image](https://github.com/user-attachments/assets/ea86d83b-057d-49cb-9957-d2aab54aa8a5)

The `Diagnostic Settings` could send the logs to a given Log Analytics workspace to help collect logs and later create Alerts from that.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing how Deployment Scripts expose run outputs and how comparable Azure resources implement Diagnostic Settings. Determine the monitoring surface, log destination behavior, and alerting requirements before identifying the affected entry points and tests. Done means Deployment Scripts expose a Monitor tab that can send relevant output logs to a selected Log Analytics workspace.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.