Contribute
Sign in
Amazon CloudWatch Application Signals

Amazon CloudWatch Application Signals

Application performance monitoring and insights.

10K+pulls13 ToolsPackaged byDocker, with additional security features including SBOMs, provenance, signing, and multi-arch support

Tools

NameDescription
list_monitored_servicesOPTIONAL TOOL for service discovery - audit_services() can automatically discover services using wildcard patterns. **IMPORTANT: For service auditing and operation analysis, use audit_services() as the PRIMARY tool instead.** **WHEN TO USE THIS TOOL:** - Getting a detailed overview of all monitored services in your environment - Discovering specific service names and environments for manual audit target construction - Understanding the complete service inventory before targeted analysis - When you need detailed service attributes beyond what wildcard expansion provides **RECOMMENDED WORKFLOW FOR SERVICE AND OPERATION AUDITING:** 1. **Use audit_services() FIRST** with wildcard patterns for comprehensive service discovery AND analysis 2. **Only use this tool** if you need basic service inventory without performance analysis 3. **audit_services() is more comprehensive** - it discovers services AND provides performance insights **AUTOMATIC SERVICE DISCOVERY IN AUDIT:** The `audit_services()` tool automatically discovers services when you use wildcard patterns: - `[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*"}}}]` - Audits all services - `[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*payment*"}}}]` - Audits services with "payment" in the name **What this tool provides:** - Basic service inventory (names, types, environments) - Service count and categorization - Key attributes for manual target construction **What this tool does NOT provide:** - Service performance analysis - Operation discovery and analysis - Root cause analysis - Actionable recommendations **For comprehensive service auditing, use audit_services() instead:** ``` audit_services( service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*"}}}]', auditors='all', ) ``` Returns a formatted list showing: - Service name and type - Key attributes (Name, Environment, Platform, etc.) - Total count of services **NOTE**: For operation auditing, use audit_services() as the primary tool instead of get_service_detail() or list_service_operations().
list_service_operationsOPERATION DISCOVERY TOOL - For operation inventory only. Use audit_services() as PRIMARY tool for operation auditing. **IMPORTANT: For operation auditing and performance analysis, use audit_services() as the PRIMARY tool instead.** **CRITICAL LIMITATION: This tool only discovers operations that have been ACTIVELY INVOKED in the specified time window.** - **Maximum time window: 24 hours** (Application Signals limitation for operation discovery) - **No results = No operation invocations** in the time window (operations exist but weren't called) - **Empty results do NOT mean operations don't exist** - they may just be inactive - **For comprehensive operation analysis regardless of recent activity, use audit_services() instead** **RECOMMENDED WORKFLOW FOR OPERATION AUDITING:** 1. **Use audit_services() FIRST** for comprehensive operation discovery AND performance analysis 2. **Only use this tool** if you need a simple operation inventory of RECENTLY ACTIVE operations 3. **audit_services() is more comprehensive** - it discovers operations AND provides performance insights even for inactive operations **What this tool provides:** - Basic operation inventory (names and available metric types) for RECENTLY INVOKED operations only - Operation count and categorization (GET, POST, etc.) for active operations - Time range for discovery (max 24 hours) **What this tool does NOT provide:** - Operations that exist but weren't invoked in the time window - Operation performance analysis - Latency, error rate, or fault analysis - Root cause analysis - Actionable recommendations **For comprehensive operation auditing, use audit_services() instead:** ``` audit_services( service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"your-service"}}}]', auditors='all', ) ``` **OPERATION DISCOVERY USE CASES (when audit_services is not sufficient):** 1. **Active operation inventory**: When you only need recently invoked operation names without performance data 2. **Traffic pattern analysis**: To see which operations are currently being used 3. **Quick active operation count**: To understand current operation activity of a service **RECOMMENDED WORKFLOW:** 1. **Use audit_services() FIRST** for comprehensive operation discovery and analysis 2. **Only use this tool** for basic inventory of recently active operations if audit_services() provides too much detail This tool provides basic operation discovery for ACTIVE operations only, but audit_services() is the primary tool for comprehensive operation auditing, performance analysis, and operation insights regardless of recent activity.