Windows and other endpoints
Check the operating-system release, agent prerequisites and required logs. Baseline Linux and macOS collection have different capabilities from Windows collection and need their own acceptance checks.
Coverage starts with the actual system
The product name is only the beginning.
Two releases of the same product can expose different metrics, permissions and management interfaces. Zentrix coverage planning starts with the device, version and evidence your team needs.
Plan across your infrastructure.
Hypervisors and virtual machines
Assess host and VM inventory, available performance data and management-platform health. Confirm the collector and required permissions for each installed platform and release.
VDI environments
Review broker, machine and session observations, then verify which user-experience fields the installed release exposes. Logon and latency detail vary by platform and API.
Network and security appliances
Select supported SNMPv3 or vendor interfaces for the required availability, interface and device-health checks. A reachable management port alone does not establish full appliance coverage.
Hardware and lifecycle
Collect available hardware identity, firmware and sensor data. Compare exact models and versions against reviewed baselines for lifecycle and firmware findings.
Applications and services
Configure relevant service, database, web and gateway checks. Define the response or observation that will establish health for each application dependency.
Agree the evidence before rollout.
- Identify the manufacturer, model, product release and management interface.
- List the health, performance, log and user-experience information you need.
- Check credentials, permissions, network access and certificate trust.
- Test a representative system and inspect the returned observations.
- Document missing fields, collection limits and the owner of each gap.
Coverage should remain measurable.
A product in an integration catalog is a setup choice, not certification of every version, feature or metric. A discovered device is a candidate until its identity and collection path are verified.
Lifecycle assessments also require evidence. End of sale, end of support and the warranty on an individual asset are different dates; none should be inferred from a model name alone.
Start with your environment.
Bring your products, versions and monitoring priorities. Build a collection plan around the evidence your team needs.