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
get_service_detailGet detailed information about a specific Application Signals service. **IMPORTANT: For operation auditing, use audit_services() as the PRIMARY tool instead.** **RECOMMENDED WORKFLOW FOR OPERATION AUDITING:** 1. **Use audit_services() FIRST** for comprehensive operation discovery and analysis 2. **Only use this tool** for basic service metadata and configuration details 3. **This tool does NOT provide operation names** - it only shows service-level metrics **What this tool provides:** - Service metadata and configuration - Platform information (EKS, Lambda, etc.) - Service-level metrics (Latency, Error, Fault aggregates) - Log groups associated with the service - Key attributes (Type, Environment, Platform) **What this tool does NOT provide:** - Operation names (GET, POST, etc.) - Operation-specific metrics - Operation-level performance data **For operation auditing, use audit_services() instead:** ``` audit_services( service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"your-service"}}}]', auditors='all', ) ``` This tool is useful for understanding service deployment details and basic configuration, but audit_services() is the primary tool for operation discovery and performance analysis.
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().
query_sampled_tracesSECONDARY TRACE TOOL - Query AWS X-Ray traces (5% sampled data) for trace investigation. āš ļø **IMPORTANT: Consider using audit_slos() with auditors="all" instead for comprehensive root cause analysis** **RECOMMENDED WORKFLOW FOR OPERATION DISCOVERY:** 1. **Use `get_service_detail(service_name)` FIRST** to discover operations from metric dimensions 2. **Use audit_slos() with auditors="all"** for comprehensive root cause analysis (PREFERRED) 3. Only use this tool if you need specific trace filtering that other tools don't provide **RECOMMENDED WORKFLOW FOR SLO BREACH INVESTIGATION:** 1. Use get_slo() to understand SLO configuration 2. **Use audit_slos() with auditors="all"** for comprehensive root cause analysis (PREFERRED) 3. Only use this tool if you need specific trace filtering that audit_slos() doesn't provide **WHY audit_slos() IS PREFERRED:** - **Comprehensive analysis**: Combines traces, logs, metrics, and dependencies - **Actionable recommendations**: Provides specific steps to resolve issues - **Integrated findings**: Correlates multiple data sources for better insights - **Much more effective** than individual trace analysis **WHY get_service_detail() IS PREFERRED FOR OPERATION DISCOVERY:** - **Direct operation discovery**: Operations are available in metric dimensions - **More reliable**: Uses Application Signals service metadata instead of sampling - **Comprehensive**: Shows all operations, not just those in sampled traces āš ļø **LIMITATIONS OF THIS TOOL:** - Uses X-Ray's **5% sampled trace data** - may miss critical errors - **Limited context** compared to comprehensive audit tools - **No integrated analysis** with logs, metrics, or dependencies - **May miss operations** due to sampling - use get_service_detail() for complete operation discovery - For 100% trace visibility, enable Transaction Search and use search_transaction_spans() **Use this tool only when:** - You need specific X-Ray filter expressions not available in audit tools - You're doing exploratory trace analysis outside of SLO breach investigation - You need raw trace data for custom analysis - **After using get_service_detail() for operation discovery** **For operation discovery, use get_service_detail() instead:** ``` get_service_detail(service_name='your-service-name') ``` **For SLO breach root cause analysis, use audit_slos() instead:** ``` audit_slos( slo_targets='[{"Type":"slo","Data":{"Slo":{"SloName":"your-slo-name"}}}]', auditors='all' ) ``` Common filter expressions (if you must use this tool): - 'service("service-name"){fault = true}': Find all traces with faults (5xx errors) for a service - 'service("service-name")': Filter by specific service - 'duration > 5': Find slow requests (over 5 seconds) - 'http.status = 500': Find specific HTTP status codes - 'annotation[aws.local.operation]="GET /owners/*/lastname"': Filter by specific operation (from metric dimensions) - 'annotation[aws.remote.operation]="ListOwners"': Filter by remote operation name - Combine filters: 'service("api"){fault = true} AND annotation[aws.local.operation]="POST /visits"' Returns JSON with trace summaries including: - Trace ID for detailed investigation - Duration and response time - Error/fault/throttle status - HTTP information (method, status, URL) - Service interactions - User information if available - Exception root causes (ErrorRootCauses, FaultRootCauses, ResponseTimeRootCauses) **RECOMMENDATION: Use get_service_detail() for operation discovery and audit_slos() with auditors="all" for comprehensive root cause analysis instead of this tool.** Returns: JSON string containing trace summaries with error status, duration, and service details