Update Azure Monitor metrics collection to utilize Managed Prometheus
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- azure, prometheus
- Domain
- documentation, observability
Research direction
Start with the Azure Monitor metrics page at https://docs.dapr.io/operations/observability/metrics/azure-monitor/ and compare its current guidance with the linked Microsoft documentation for Managed Prometheus. Update that page to describe and link to the Managed Prometheus solution instead of the legacy strategy, then verify the rendered documentation and links.
Written by the indexing model from the issue text.
Description
What content needs to be modified?
https://docs.dapr.io/operations/observability/metrics/azure-monitor/ describes the azure monitor metric scraping.
Based on my understanding this describes the legacy strategy to send Prometheus metrics from a Kubernetes cluster to a Log Analytics workspace.
https://learn.microsoft.com/en-us/azure/azure-monitor/containers/container-insights-prometheus-logs?tabs=cluster-wide
Describe the solution you'd like
Update the documentation and point to the Managed Prometheus solution instead:
https://learn.microsoft.com/en-us/azure/azure-monitor/containers/kubernetes-monitoring-enable?tabs=azure-cli
Where should the new material be placed?
https://docs.dapr.io/operations/observability/metrics/azure-monitor/
- Dominant language
- SCSS
- Stars
- 1k
- Forks
- 796
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 16
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dapr/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
content/missing-information
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
content/incorrect-information
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
content/incorrect-information
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100