netdata
Official@netdata · USA
Offers high-resolution observability and diagnostic triage for distributed infrastructure, databases, and containerized environments via standardized telemetry and signal-based analysis.
Agent Skills by netdata
Showing 78 vetted skills indexed across 3 GitHub repositories.
project-writing-collectors
Standardize the development and maintenance of Netdata Agent data collection plugins and modules.
learn-site-structure
Analyze and manage the documentation pipeline for publishing source repository content to the Netdata learn site.
project-build-static-binary
Automate the creation of self-extracting static Netdata installers for diverse Linux architectures.
codacy-audit
Automate local static analysis and PR issue triage for Codacy-monitored repositories.
project-prometheus-profiles
Create, validate, and install Netdata Prometheus collector chart profiles for infrastructure monitoring.
project-snmp-profiles-authoring
Validate and author Netdata SNMP profile YAML configurations for infrastructure monitoring.
project-query-corpus
Validate Netdata query engine correctness using an end-to-end black-box testing suite.
query-agent-events
Diagnose Netdata agent crashes and fatal errors by analyzing systemd-journal events across the infrastructure fleet.
mirror-netdata-repos
Maintain a local mirror of Netdata source repositories for efficient cross-repo code analysis.
project-snmp-trap-profiles-authoring
Validate and generate Netdata SNMP trap profile YAML configurations for infrastructure observability.
learn-pr-preview
Build and inspect local documentation previews from pull request branches for validation.
project-health-alert-authoring
Configure and validate Netdata health alerts using standardized NIDL-compliant alert definitions.
project-create-topology
Automate the creation and migration of Netdata topology producers and schema-compliant Function payloads.
integrations-lifecycle
Manage the end-to-end lifecycle of Netdata integration metadata, documentation, and taxonomy artifacts.
project-writing-go-modules-framework-v2
Implement and migrate Netdata Go collectors using the framework V2 architecture and patterns.
query-netdata-cloud
Construct REST API queries to retrieve metrics, logs, topology, and configuration data from Netdata Cloud infrastructure.
query-netdata-agents
Query Netdata Agent HTTP APIs directly for metrics, logs, alerts, and streaming topology data.
query-snmp-traps
Analyze SNMP trap logs and extract structured event data from Netdata Agent journal files.
project-netdata-vendoring
Analyze plugin-ipc changes and plan migration into Netdata's vendored source.
troubleshoot-redis
Diagnose Redis failures using Netdata MCP signals and a triage tree.
troubleshoot-zfs
Diagnose ZFS pool and performance incidents using Netdata-observed metrics via MCP queries.
troubleshoot-nvme
Troubleshoot NVMe health by querying Netdata via MCP and mapping anomalies to playbook domains.
netdata-config-from-requirements
Convert written requirements into a Netdata configuration bundle with YAML and a verification runbook.
troubleshoot-vmware-vsphere
Diagnose VMware vSphere incidents using Netdata signals via MCP.
Frequently Asked Questions About netdata
FAQPage SchemaWhat specific infrastructure tasks can be performed using these capabilities?▼
These capabilities enable real-time diagnosis of infrastructure, database, and container failures. Users can perform root-cause analysis on systems like Kubernetes, Redis, PostgreSQL, and Nginx by querying live health signals and mapping symptoms to established failure archetypes and diagnostic decision trees.
Which technical personas benefit most from these diagnostic skills?▼
Site Reliability Engineers (SREs), DevOps practitioners, and database administrators benefit most. These skills are designed for technical teams responsible for maintaining high-availability environments, managing complex distributed systems, and reducing mean-time-to-resolution (MTTR) through structured, signal-based troubleshooting.
What are the prerequisites for integrating these diagnostic signals?▼
Integration requires an existing Netdata deployment and the configuration of OpenTelemetry collectors or OTLP/gRPC exporters. Systems must be instrumented to emit telemetry, which is then queried via the Model Context Protocol (MCP) to facilitate the diagnostic triage and signal mapping processes.