Keep sensor meaning intact
Temperature, power draw, battery state and interface traffic measure different things. Preserve the device source, unit and last observation time. An absent sensor is unavailable, not a zero reading.
AOT OpsAI solutions
Connect infrastructure health with supporting conditions.
Understand supported server, network, UPS, PDU and environmental observations with explicit coverage and collection limits.
Separate control from monitoring
OpsAI observes supported sources; it does not operate building controls or replace an electrical safety system. Private facility protocols need an approved local collection path.
Review coverage before escalation
Establish which racks, circuits and service dependencies are actually observed. A partial availability report describes covered assets and collection gaps, rather than claiming whole-facility uptime.
Map logical infrastructure to the supporting equipment
Review supported hypervisor, server, network and facility sources with their owners. Distinguish a guest VM from its host and storage, then document the supporting power and environmental devices where their observations are available. Hypervisor disk allocation is not free space inside a guest filesystem. Keep these meanings separate when comparing current capacity with the period of an incident.
Agree on evidence for the initial evaluation
Select an approved area and confirm the identity, units, timestamps and freshness of its returned readings. Review a planned test with the responsible operator and check how the chosen report describes missing coverage. Collector host sizing must follow a qualified workload rather than an assumed number of racks. Site access, engineering assistance, escalation hours and any deployment work are separately scoped with AOT.