skills.rest
netdata
netdataOFFICIAL
Explore all skills by this author →
WebsiteGitHub

troubleshoot-docker-engine

Diagnose Docker Engine incidents via Netdata MCP queries and operator playbook triage.

1|Updated Apr 17, 2026
Search Tags:#troubleshooting#mcp#observability#docker#netdata#docker-engine#operator-playbook
One-click install
npx skills add https://github.com/netdata/skills --skill troubleshoot-docker-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshoot-docker-engine
Source: https://github.com/netdata/skills/tree/main/skills/troubleshoot-docker-engine
Command: npx skills add https://github.com/netdata/skills --skill troubleshoot-docker-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you diagnose Docker Engine operational problems by guiding an agent through structured triage using Netdata’s Docker Engine health signals via MCP.

Core Features & Use Cases

  • MCP-based signal triage: Uses Netdata MCP calls (node discovery, metrics queries, anomaly finding, and correlated metrics) to pinpoint where the failure is occurring.
  • Operator playbook decision tree: Routes the agent through the same failure-pattern logic the Netdata operator playbook uses, tailored to Docker Engine contexts.
  • Remediation verification loop: Re-runs the same MCP queries after remediation to confirm signals return to expected ranges and drift back does not occur.

Quick Start

Ask your agent: Diagnose my Docker Engine incident using Netdata MCP and the Docker Engine operator playbook triage path, and verify the fix by re-running the core docker_engine context queries.

Frequently Asked Questions about troubleshoot-docker-engine

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

FAQPage Schema
How do I troubleshoot Docker Engine issues using Netdata?▼

You can diagnose Docker Engine operational problems by guiding an agent through structured triage using Netdata's Docker Engine health signals via MCP, applying an operator playbook diagnostic tree for incidents like elevated errors or resource exhaustion.

What is the best way to triage a Docker Engine incident when a Netdata alert is firing?▼

Apply the operator playbook diagnostic tree through MCP queries for node discovery, anomaly ranking, and correlated-metric analysis to pinpoint exactly where the Docker Engine failure is occurring during an active alert.

Can I verify Docker Engine remediation using Netdata MCP queries?▼

Yes, a remediation verification loop re-runs the same MCP queries after a fix to confirm Docker Engine signals return to expected ranges within known docker_engine.* chart contexts and ensures drift back does not occur.

Does this Docker Engine troubleshooting approach work for resource exhaustion and unexpected restarts?▼

Yes, this approach applies to service incidents including resource exhaustion, unexpected restarts, elevated errors, latency, saturation, and on-call triage for Docker Engine instances.

What Docker Engine metrics do I need to check during on-call triage?▼

During on-call triage, check Docker Engine health signals by retrieving context-scoped metrics and analyzing correlated metrics across known docker_engine.* chart contexts using MCP queries.

Related Skills

Explore More Software Engineering Skills→
netdatanetdata
1

troubleshoot-uwsgi

Diagnose uWSGI failure modes using Netdata signals via MCP queries.

Official
Intermediate
netdatanetdata
1

troubleshoot-proxysql

Diagnose ProxySQL incidents by mapping symptoms to Netdata signal domains.

Official
Advanced
netdatanetdata
1

troubleshoot-nvidia-gpu

Triage Nvidia GPU failures by mapping Netdata MCP metrics to signal-domain rule files.

Official
Advanced
netdatanetdata
1

troubleshoot-docker

Diagnose Docker infrastructure failures using Netdata MCP health signals.

Official
Advanced