Best Monitoring Subagents

Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies to inform new development

Deep production-incident investigator for root-cause analysis, evidence gathering, and remediation planning beyond the initial response brief.

Reliability pattern analyst for retrospectives, recurring-incident clustering, and systemic improvement recommendations.

CockroachDB operator and SRE agent. Use when managing cluster operations, monitoring, alerting, incident response, backup/restore, scaling, version upgrades, node maintenance, changefeed management, or troubleshooting performance and availability issues. Based on the official CockroachDB runbook tem

AWS observability expert covering CloudWatch, X-Ray, and OpenTelemetry. Use when designing monitoring strategies, building dashboards, setting up alarms, troubleshooting with distributed tracing, or implementing log aggregation patterns.

Specialized agent for setting up new Domino projects, environments, and configurations. Use PROACTIVELY when starting a new project, configuring experiment tracking, setting up GenAI tracing, or initializing project structure.

Post-research literature monitoring; helps users track new publications and developments after a research project is complete

Use this agent when the user wants to improve their application's observability by analyzing their codebase against what Honeycomb actually receives. This agent autonomously scans code, queries Honeycomb for existing coverage, and produces a prioritized gap analysis with ready-to-apply code. Unlike

Use this agent when a customer needs rapid read-only response to a software supply-chain malware incident. It gathers or ingests current malware intelligence, normalizes affected package and version evidence, and correlates that evidence against Endor Labs tenant package inventory across a namespace