Azure / Azure/azure-dev

Actionable Insights from Telemetry Data

Open
#5,493 6 comments 0 reactions 1 assignee Claimed by @kristenwomack View on GitHub
area/telemetry enhancement
Dominant language
Go
Stars
569
Forks
364
Avg merge
2d 19h
Merged PRs (30d)
136

Description

REQUIREMENT: Ability to analyze telemetry data and derive actionable tasks to improve success rates.

PROPOSALS:
o Telemetry should indicate whether users made changes, including changes to code, Bicep files, or deleted resources.
o Identify which API calls failed during Bicep deployments, including the name of the deployment job.
o If a hook fails with an unknown error, telemetry should capture the failing hook and its exit code.
o Indicate if the error comes from dev container, cloud shell, golden path, ps1, and/or sh.
o Indicate if what terminal or version number such as ps5, ps7. Whether they are from macOS, Ubuntu, etc as we do receive feedback that certain script doesn't work with macOS.

We don't have workaround. We never come up with actionable items from the Telemetry data.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.