project-snmp-trap-profiles-authoring

Validate and generate Netdata SNMP trap profile YAML configurations for infrastructure observability.

80.4k|6.6k|Updated Jun 17, 2013
One-click install
npx skills add https://github.com/netdata/netdata --skill project-snmp-trap-profiles-authoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-snmp-trap-profiles-authoring
Source: https://github.com/netdata/netdata/tree/main/.agents/skills/project-snmp-trap-profiles-authoring
Command: npx skills add https://github.com/netdata/netdata --skill project-snmp-trap-profiles-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires go, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complexity of maintaining consistent, high-performance SNMP trap profiles across large-scale network infrastructure, preventing configuration errors and ensuring compatibility with Netdata's trap subsystem.

Core Features & Use Cases

  • Profile Validation: Enforces strict taxonomy for categories, severities, and metric cardinality to prevent configuration drift.
  • Generator Management: Provides a standardized workflow for regenerating OOB trap profile packs using the snmptrapprofilegen Go helper.
  • Use Case: When adding a new vendor MIB to your monitoring stack, use this Skill to ensure your trap profile adheres to the required schema, MIB-qualified naming conventions, and metric rules before deployment.

Quick Start

Use the snmp trap profile authoring skill to validate the new vendor profile in the default directory.

Frequently Asked Questions about project-snmp-trap-profiles-authoring

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

FAQPage Schema
How do I add a new SNMP trap profile to Netdata?

Create a new YAML file following the schema defined in profile-format.md, ensuring all trap names are MIB-qualified and varbinds are properly resolved. Use the snmptrapprofilegen helper to validate your profile against the closed taxonomy of categories and severities.

Why must trap names be MIB-qualified?

MIB-qualified names (e.g., IF-MIB::linkDown) ensure global uniqueness across different vendor MIB modules. Bare symbolic names are often reused, which causes collisions and incorrect trap routing within the Netdata trap subsystem.

Can I use custom categories in my trap profiles?

No, categories must belong to the closed set of 8 defined in the taxonomy (e.g., state_change, security, auth). Cross-cutting concerns should be handled using labels rather than introducing new category slugs.

How do I handle high-cardinality data in trap metrics?

High-cardinality data like MAC addresses or source IPs must be excluded from metric labels to prevent cardinality explosion. Instead, include these details in the trap description or indexed journal fields where they remain searchable without impacting time-series performance.