telemetry-ops

Aggregates syslog, SNMP traps, IPFIX flows, and gNMI telemetry from network devices.

650|182|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill telemetry-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: telemetry-ops
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/telemetry-ops
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill telemetry-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Network events are scattered across syslog, SNMP traps, flow records, and streaming telemetry, making it hard to see the full picture of network health or investigate incidents that span multiple data sources.

Core Features & Use Cases

  • Unified Receiver Orchestration: Coordinates four telemetry receivers (syslog on UDP 514, SNMP traps on UDP 162, IPFIX/NetFlow on UDP 2055, gNMI on TCP 57400) through their respective MCP servers.
  • Multi-Source Incident Investigation: Correlates syslog errors, linkDown traps, flow anomalies, and real-time gNMI interface state around a specific incident window.
  • Device Onboarding Guidance: Provides Cisco Catalyst 9300 configuration snippets for syslog, SNMP traps, IPFIX export, and gNMI to onboard devices to monitoring.
  • Use Case: When a network issue is reported at 3pm, query syslog for errors, check SNMP traps for link events, analyze flows for traffic anomalies, and subscribe to gNMI for live interface state, all from one workflow.

Quick Start

Start all telemetry receivers on their default ports and show me a summary of network health from every source.

Frequently Asked Questions about telemetry-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I collect syslog, SNMP traps, and NetFlow from network devices?

Point each device at the NetClaw receivers: syslog to UDP 514, SNMP traps to UDP 162, and IPFIX/NetFlow export to UDP 2055. Then start the corresponding MCP receivers and query events through the agent.

How to configure a Cisco Catalyst 9300 for telemetry export?

Configure logging host with UDP 514 for syslog, snmp-server host for traps, a flow exporter with IPFIX to UDP 2055, and enable netconf-yang plus gnmi-yang for streaming telemetry. The skill provides ready-to-use configuration snippets for each.

What is the difference between IPFIX and gNMI telemetry?

IPFIX exports flow records over UDP 2055 showing who is talking to whom and how much bandwidth is used. gNMI streams structured device state over gRPC on TCP 57400, such as real-time interface counters and operational data.

Can I receive telemetry from remote devices over the internet?

Yes, but ngrok does not support UDP, so use Pinggy, Tailscale, or LocalXpose to tunnel UDP traffic for syslog, SNMP traps, and IPFIX. gNMI uses TCP and works with standard tunneling.

What are the limitations of this telemetry setup?

All receivers use in-memory storage, so collected data is lost on restart. There is no built-in cross-source correlation; the agent performs correlation at query time, and each receiver runs independently.