Configured
Profile, Management IP and allowed collection path are saved.
Optional Infrastructure Monitoring
Live signals, attached to physical reality.
Enable Monitoring per Client, then add measured network, power and environmental evidence to the exact Equipment, Port, PDU, Rack and Site your teams already operate.
ILLUSTRATIVE PRODUCT FLOW · NOT LIVE CUSTOMER DATA
Network Port health
18 / 24 observedIF-MIB · 45 s ago
Monitoring contract
Configured is not the same as observed.
Tenqora separates setup, reachability, polling and evidence so a saved IP address or SNMP Profile never becomes a false green status.
Reachable
Local, Agent, VPN or approved vendor-cloud route passes diagnostics.
Polled
A read-only protocol returns a real observation from the target.
Trusted evidence
Source, timestamp, unit, freshness and quality are retained together.
Collection paths
Reach private infrastructure without opening the origin.
Choose the path that matches each Site boundary. Monitoring remains read-only unless a separately governed change workflow is introduced.
Tenqora Agent
Outbound-only collection with tenant-scoped mTLS identity.
SNMP · sensors · future adaptersVPN route
WireGuard, OpenVPN or IPsec/IKEv2 as primary or backup access.
Private Management networksVendor cloud
Read-only identity and observations where an official API supports them.
Never implies private SNMP reachabilityDirect network
Backend collection only inside an explicitly allowed routed boundary.
CIDR-scoped accessCoverage
One optional layer across active Equipment.
Switches are only one case. Servers, routers, firewalls, managed PDU, environmental sensors and other active Equipment can use the same evidence rules when a compatible Profile and collector exist.
Network
Interface state, counters, errors, throughput, identity and supported VPN observations through read-only profiles.
Power
Feed, phase, bank and outlet readings in W, kW, VA, kVA, A and V without allocating missing values.
Environment
Rack-air and internal Equipment sensors remain separate, with freshness and data-quality states.
Equipment health
CPU, memory, fans, PSU, storage and vendor-reported health where the active profile exposes them.
Alerts
Threshold, stale source, missing poll and rate-of-change events with controlled deduplication.
History
Current evidence, operational trends and bounded history stay connected to the physical object.
Monitoring development
A staged path from device evidence to service context.
The roadmap is explicit: current capability is distinguished from planned work, and planned work is never marketed as live telemetry.
Physical infrastructure evidence
- SNMP Profiles and MIB management
- Agent, local, VPN and vendor-cloud paths
- Port, PDU and environmental observations
- Diagnostics, freshness and source identity
Fleet discovery and correlation
- Broader IP-range discovery
- LLDP/FDB and interface relationship evidence
- Saved topology and role-based monitoring views
- Capacity and anomaly workflows
Service and software observability
- Optional OpenTelemetry metrics, logs and traces
- Service Map over physical and logical evidence
- Explainable cross-domain incident context
- Governed automation after explicit approval
Monitoring is optional