One-click install
npx skills add https://github.com/automateyournetwork/netclaw --skill syslog-receiver
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: syslog-receiver
Source: https://github.com/automateyournetwork/netclaw/tree/main/workspace/skills/syslog-receiver
Command: npx skills add https://github.com/automateyournetwork/netclaw --skill syslog-receiver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Network devices generate syslog events continuously, but without a central collector these messages are lost, making real-time monitoring and post-incident investigation difficult. This Skill collects syslog messages from routers, switches, and firewalls and lets you query them by severity, hostname, source IP, or content.

Core Features & Use Cases

  • UDP Syslog Collection: Start a receiver that listens for both RFC 5424 (modern) and RFC 3164 (BSD/Cisco) formatted messages from network devices.
  • Filtered Querying: Search collected messages by severity level, facility, hostname, source IP, or keyword content, and retrieve full details of individual entries.
  • Severity Analytics: Get message counts grouped by severity to quickly spot spikes in CRITICAL, ERROR, or WARNING events.
  • Use Case: During an outage investigation, query all messages with severity ERROR or higher from a specific device IP in the last hour, then pull full message details to identify the root cause such as an interface flap.

Quick Start

Ask the agent to start the syslog receiver on port 10514 and then show all error messages received in the last hour.

Frequently Asked Questions about syslog-receiver

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

FAQPage Schema
How do I collect syslog messages from Cisco routers and switches?

Start the syslog receiver on a UDP port such as 10514, then configure your devices to send syslog to that port. The receiver accepts both RFC 5424 and RFC 3164 (BSD/Cisco) formats and stores messages for querying.

How do I search syslog messages by severity or hostname?

Use the syslog_query tool with filters like severity_max to cap severity level, hostname or source_ip to target a device, and message_contains for keyword searches. Use syslog_get_message to retrieve full details of a specific entry.

Does the syslog receiver support TCP or only UDP?

The receiver supports UDP only; TCP syslog is not supported. It listens on a configurable port (default 514) and bind address, with one receiver instance allowed per port.

What syslog formats are supported by this receiver?

Both RFC 5424 (modern structured syslog) and RFC 3164 (BSD/Cisco legacy format) are supported, so messages from most network devices including Cisco routers, switches, and firewalls can be parsed.

What are the limitations of this syslog collection approach?

Messages are stored in memory only, so all data is lost when the receiver restarts. There is no persistent storage or export, retention defaults to 24 hours, and rate limiting defaults to 1000 messages per second.