One agent sees the query and the wire.
Most tools watch one layer and guess at the other. Netovair collects both from a single agent and correlates them in one engine, so the answer to "database or network?" arrives with the alert.
Everything you need to answer the question — in one console.
The correlation engine
Every metric is timestamped to a shared clock and mapped onto your topology. When a database symptom and a network event line up in time and in path, the engine links them and ranks the likely cause. Your first notification reads "replication lag caused by uplink saturation on core-switch-a" — not just "replication lag."
Database layer
Query latency percentiles, slow-query capture with plans, lock contention, connection-pool health, and replication lag across PostgreSQL, MySQL, Redis, and MongoDB.
Network layer
SNMP counters, NetFlow/sFlow, and active probes give you packet loss, jitter, interface saturation, and DNS resolution health per path — not just an up/down ping.
Live topology map
Hosts, databases, switches, and their dependencies — auto-discovered and always current. During an incident, the affected path lights up so the blast radius is obvious at a glance.
Smart alerting
Per-metric baselines learned from your own history, alerts grouped into a single incident, and delivery to Slack, PagerDuty, or email. One real problem produces one page.
Security layer
Suspicious database access and exfiltration signals, configuration and compliance drift, and unauthorized device or port changes — correlated on the same timeline as performance. Part of the Database + Network + Security plan.
Install to first insight in an afternoon.
The agent is a single static binary. The collector ships as a container. Nothing about your stack has to change.
Deploy the agent
One command per host. It auto-discovers local databases and interfaces and starts streaming immediately.
curl -sSL get.netovair.com | shPoint it at your gear
Add switches and routers by SNMP community or flow export. The topology map builds itself as devices report in.
netovair add-device 10.0.0.1 --snmpRoute the alerts
Connect Slack or PagerDuty, accept the learned baselines, and hand the guesswork to the correlation engine.
netovair alerts connect pagerdutyWorks with the stack you already run.
No rip-and-replace. Netovair reads from the databases and network gear you have and pushes alerts into the tools your team already lives in.
Databases
PostgreSQL · MySQL / MariaDB · Redis · MongoDB. Read-only monitoring users; no schema changes required.
Network
SNMP v2c/v3 · NetFlow · sFlow · active ICMP/TCP probes. Any switch, router, or firewall that speaks the standards.
Notifications
Slack · PagerDuty · Opsgenie · email · generic webhook. Grouped so one incident is one page.
Deploy anywhere
Netovair Cloud, self-hosted on-prem, or fully air-gapped. Your telemetry can stay inside your network end to end.
Cloud databases
Amazon RDS & Aurora, Google Cloud SQL, Azure Database. Monitor managed engines with the same console.
API & export
Query your metrics over a documented API, or stream to your existing data lake. Your data stays portable.
What the on-call actually sees.
One console, three views of the same incident — the map of what's affected, the timeline that links the layers, and the security signals riding alongside.
Live topology
Auto-discovered hosts, databases, and network gear. The affected path lights up so the blast radius is obvious at a glance.
Correlation timeline
Database and network spikes share one clock. When they line up, the engine links them and names the cause.
Security signals
Threats to the data path — exfiltration patterns, config drift, unexpected port changes — surface on the same timeline as performance.
See it correlate your own stack.
Five hosts are free forever. Install the agent and watch both layers land on one timeline.