Skip to content

Management tools and performance collector ​

Generated by scripts/docs/New-CollectorReferencePages.ps1 from the collector definitions. Do not edit by hand.

PropertyValue
Idmanagement-performance
FunctionInvoke-RangerManagementPerformanceCollector
Classcore
Coversmanagement-tools, performance
Required targetcluster
Required credentialcluster
Manifest domainsdomains.managementTools, domains.performance

Access and permissions ​

WinRM to the nodes for services, installed management agents and a short performance sample. 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.managementTools ​

agents, summary, tools

domains.performance ​

compute, events, networking, nodes, outliers, storage, summary

When it is skipped, degraded or failed ​

Registry reads for optional agents (for example Operations Manager) that are absent are not errors; other failed reads 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.

Released under the MIT License.