Storage and networking collector
Generated by
scripts/docs/New-CollectorReferencePages.ps1from the collector definitions. Do not edit by hand.
| Property | Value |
|---|---|
| Id | storage-networking |
| Function | Invoke-RangerStorageNetworkingCollector |
| Class | core |
| Covers | storage, networking |
| Required target | cluster |
| Required credential | cluster |
| Manifest domains | domains.storage, domains.networking |
Access and permissions
WinRM to the nodes (Storage, NetAdapter, Hyper-V, Network ATC, DCB cmdlets). Optional offline switch or firewall configuration files. 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.storage
csvs, physicalDisks, pools, qos, replica, sofs, storagePaths, summary, virtualDisks, volumes
domains.networking
adapters, clusterNetworks, dns, firewall, hostVirtualNics, intents, logicalNetworks, nodes, proxy, sdn, summary, vSwitches
When it is skipped, degraded or failed
Core collector: it fails the run when no storage or network data can be read from any node. Individual reads that fail are listed in the collector degradations.
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.
Azure Local 12.2609 (latest) coverage
| Item | Manifest path | Microsoft Learn |
|---|---|---|
| Disaggregated / SAN indicators | domains.storage.architectureIndicators | https://learn.microsoft.com/azure/well-architected/service-guides/azure-local |
Details: Platform evidence for 12.2609.