Step-by-step tutorials for onboarding devices, configuring vendor protocols, wiring up alerting, and everything in between, screenshots included, written as a working reference for how the product should behave.
The fastest path from a new Zynty account to a device reporting live data on your dashboard.
Collectors are the bridge between your network and Zynty Cloud. Here's how to size, place and install one.
What to open, what to leave closed, and how the collector fits into a network that already has firewalls, VPNs and segmentation in place.
The core workflow every other tutorial in this section builds on: getting one device from "not monitored" to reporting data.
A lean configuration for a one-person (or one-and-a-half-person) network team that doesn't need elaborate role structures.
Structure sites, groups and collectors so a large network stays navigable instead of becoming one giant device list.
Keep each client's devices, alerts and reports cleanly separated while still managing everything from one place.
Monitor physical network gear and cloud infrastructure side by side, without treating them as two separate tools.
Keep a network team spread across time zones working from the same picture of the network.
Give a network operations center the always-on dashboard view it needs, with clean handoffs between shifts.
Give someone visibility for a compliance review or a short-term engagement without handing over change access.
Organize a campus network with dozens of buildings and a mix of managed and BYOD traffic.
Configure access, retention and encryption defaults appropriately for a network carrying sensitive patient data.
Monitor hundreds of small, similar sites (stores, branches, restaurants) without hand-configuring each one individually.
Enable a read-only SNMP v2c community (or v3 user) on Cisco IOS and IOS-XE, then add the switch in Zynty.
Set up a read-only SNMP community on Junos-based EX and QFX switches.
Enable SNMP polling on Arista EOS, common in leaf-spine data center fabrics.
Set up SNMP on ArubaOS-CX (and legacy ArubaOS-Switch) hardware.
Enable SNMP on RouterOS, common at branch sites and smaller edge deployments.
Turn on NetFlow v9 export so Zynty can build traffic and conversation analysis for a router's interfaces.
Configure sampling and an IPFIX flow-server export on Junos.
Set up sampled flow export on Arista EOS, well suited to high-throughput core and spine switches.
Add a MySQL or MariaDB server as a monitored device and get query throughput, connections, replication and slow-query visibility.
Add a PostgreSQL server as a monitored device using the built-in pg_monitor role.
Turn on the slow query log so Zynty can surface the queries actually costing you performance.
Keep an eye on how far behind your read replicas are, before an application starts reading stale data.
Add MongoDB nodes as monitored devices and track replica set health alongside the rest of your infrastructure.
Track memory usage, connected clients and command throughput on Redis and Redis-compatible caches.
Add a SQL Server instance and track wait stats, connections and job/agent health.
Add an Oracle instance and get session, tablespace and wait-event visibility.
Track cluster health, shard state and indexing rate for Elasticsearch or OpenSearch.
Get paged before a database runs out of available connections, not after your application starts throwing errors.
Catch runaway disk growth from an unbounded table, a stuck vacuum, or forgotten log files before it becomes an outage.
For databases without native Zynty support, ingest metrics from an existing Prometheus-format exporter instead.
Send device logs to your collector so Zynty can correlate log events with alerts and change history.
Encrypt log transport between a device and your collector instead of sending plaintext UDP syslog.
SSH access lets Zynty pull metrics that aren't exposed over SNMP, and back up device configurations.
Monitor Windows Server metrics and services without installing a third-party agent.
Onboard hundreds of devices at once instead of adding them one at a time.
Scan an IP range and add what responds, faster than hunting down every device manually.
Structure your inventory so dashboards, alert routing and reports reflect how your network is actually organized.
A step-by-step path for diagnosing the most common reason a device won't report data.
Keep a versioned history of every device's configuration without remembering to run a backup manually.
Roll a device back to a known-good configuration from its version history.
When Zynty detects a config change, see exactly what changed, line by line, before deciding what to do about it.
Get pinged the moment a device's configuration changes, filtered to the devices and change types you actually care about.
Search across every device's live configuration to find and fix policy violations network-wide.
The difference between a device's saved configuration and what it's actually running right now, and why that gap matters.
Deploy the same configuration change to dozens or hundreds of devices at once, on a schedule or on demand.
Keep configuration and runtime state data current across your network without manually triggering a collection.
Turn raw metrics into alerts that page someone only when it actually matters.
Route alerts and change notifications straight into the channels your team already watches.
Escalate critical alerts to your on-call rotation instead of relying on someone watching a dashboard.
Stop planned work from paging your on-call rotation.
Automatically open a tracked issue when a critical alert fires or an unexpected configuration change is detected.