YADRO releases monitoring templates for KORNFELD switches
YADRO has released Zabbix templates and Grafana dashboards for KORNFELD switches. We examine the package, its limits and checks required before production use.
Contents
On 9 July 2026, YADRO announced the availability of KORNFELD.SATELLITES, a toolkit for connecting KORNFELD switches to enterprise monitoring systems. The first release includes ready-made Zabbix templates and Grafana dashboards.
The package addresses the stage between basic device configuration and production handover. Network teams do not have to define every metric, create data items and build operational dashboards from scratch for each new group of switches.
What the first release contains
According to the vendor, KORNFELD.SATELLITES covers four groups of operational data:
- overall hardware-platform health;
- readings from built-in sensors;
- network-interface status and metrics;
- network-process operation.
The templates standardize data collection in Zabbix, while the Grafana dashboards present that data for diagnosis and routine supervision. Components are distributed through YADRO’s service portal without a separate licence, include documentation and are supported by the vendor’s service team.
This is not a separate monitoring system that must be deployed alongside an established platform. KORNFELD.SATELLITES is intended to integrate the hardware with tools already used by operations teams. For an organization with common monitoring procedures, this can avoid another isolated console.
How templates can shorten commissioning
Installing a switch does not make a network ready for production traffic. Before handover, a team still has to validate metrics, set thresholds and event routing, prepare dashboards, associate the device with inventory records and document failure procedures.
Ready-made templates reduce the repetitive part of that work and give identical device models a consistent set of signals. Alerting rules, however, still need site-specific context: port utilization, redundancy design, permitted temperature ranges, maintenance windows and the business services affected by each switch.
Details not provided by the announcement
The release does not enumerate every metric and trigger, supported Zabbix and Grafana versions, switch models, maximum tested scale or the template update cycle. It also does not describe packaged integrations with a CMDB, incident-management tools or other observability platforms.
Before rollout, an infrastructure team should confirm:
- compatibility across hardware models and firmware versions;
- update delivery and backward compatibility of templates;
- protocols, service accounts and network ports in use;
- polling intervals and monitoring-platform load;
- discovery of new interfaces and removal of obsolete items;
- whether templates can be customized without losing vendor support;
- export of events to a service desk and central log environment.
A practical pilot
A useful pilot should include switches with several roles, such as access, aggregation and a data-centre core or fabric. After importing the templates, the team should validate inventory data, interface counters, temperatures and power-supply status, then reproduce controlled events.
The minimum scenario set includes a redundant-link failure, rising interface errors, loss of one power supply, a temperature threshold breach and loss of the monitoring channel itself. For every event, test detection time, deduplication, priority and the availability of a clear response instruction.
Our guide to infrastructure observability covers the relationship between metrics, logs, traces and alerts. To separate useful signals from noise, device-level telemetry should also be tied to SLIs, SLOs and error budgets.
Practical conclusion
KORNFELD.SATELLITES addresses an operational task: connecting new switches to an existing Zabbix and Grafana environment more quickly. Its value lies less in an individual dashboard than in a repeatable metric set and a more predictable handover to operations.
Ready-made templates should not be treated as a final production configuration. Teams still need to validate them against deployed hardware and software versions, tune thresholds to the network topology and connect alerts to recovery procedures.
Primary source: YADRO: tools for faster network-infrastructure commissioning
