Monitoring and observability collector
Generated by
scripts/docs/New-CollectorReferencePages.ps1from the collector definitions. Do not edit by hand.
| Property | Value |
|---|---|
| Id | monitoring-observability |
| Function | Invoke-RangerMonitoringCollector |
| Class | core |
| Covers | monitoring, observability |
| Required target | azure |
| Required credential | azure |
| Manifest domains | domains.monitoring |
Access and permissions
Azure Resource Manager (Reader) for Azure Monitor, Log Analytics, data collection rules and endpoints, and Azure Update Manager. Read-only.
Output
Top-level keys of each domain, as seen in the fixture manifest (tests/maproom/Fixtures/synthetic-manifest.json). Collectors can add keys between releases; the manifest schema keeps domain payloads open.
domains.monitoring
alerts, ama, dce, dcr, health, insights, summary, telemetry, updateManager
When it is skipped, degraded or failed
Skipped when Azure is not reachable or no Azure credential is configured.
The collector status in the manifest is one of success, partial, failed, skipped or not-applicable. Since v2.7.0 the entry also carries degraded, degradationCount and degradations (source and message of every non-fatal read that failed), and a degraded collector adds an informational finding. Debug-level detail is in ranger.log.