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
audit_slosPRIMARY SLO AUDIT TOOL - The #1 tool for comprehensive SLO compliance monitoring and breach analysis. **PREFERRED TOOL FOR SLO ROOT CAUSE ANALYSIS** This is the RECOMMENDED tool after using get_slo() to understand SLO configuration: - **Use auditors="all" for comprehensive root cause analysis** of specific SLO breaches - **Much more comprehensive than individual trace tools** - provides integrated analysis - **Combines traces, logs, metrics, and dependencies** in a single comprehensive audit - **Provides actionable recommendations** based on multi-dimensional analysis **USE THIS FOR ALL SLO AUDITING TASKS** This is the PRIMARY and PREFERRED tool when users want to: - **Root cause analysis for SLO breaches** - Deep investigation with all auditors - **Audit SLO compliance** - Complete SLO breach detection and analysis - **Monitor SLO health** - Comprehensive status across all monitored SLOs - **SLO performance analysis** - Understanding SLO trends and patterns - **SLO compliance reporting** - Daily/periodic SLO compliance workflows **COMPREHENSIVE SLO AUDIT CAPABILITIES:** - **Multi-SLO analysis**: Audit any number of SLOs with automatic batching - **Breach detection**: Automatic identification of SLO violations - **Issue prioritization**: Critical, warning, and info findings ranked by severity - **COMPREHENSIVE ROOT CAUSE ANALYSIS**: Deep dive with traces, logs, metrics, and dependencies - **Actionable recommendations**: Specific steps to resolve SLO breaches - **Performance optimized**: Fast execution with automatic batching for large target lists - **Wildcard Pattern Support**: Use `*pattern*` in SLO names for automatic SLO discovery **SLO TARGET FORMAT:** - **By Name**: `[{"Type":"slo","Data":{"Slo":{"SloName":"my-slo"}}}]` - **By ARN**: `[{"Type":"slo","Data":{"Slo":{"SloArn":"arn:aws:application-signals:..."}}}]` **WILDCARD PATTERN EXAMPLES:** - **All SLOs**: `[{"Type":"slo","Data":{"Slo":{"SloName":"*"}}}]` - **Payment SLOs**: `[{"Type":"slo","Data":{"Slo":{"SloName":"*payment*"}}}]` - **Latency SLOs**: `[{"Type":"slo","Data":{"Slo":{"SloName":"*latency*"}}}]` - **Availability SLOs**: `[{"Type":"slo","Data":{"Slo":{"SloName":"*availability*"}}}]` **AUDITOR SELECTION FOR DIFFERENT AUDIT DEPTHS:** - **Quick Compliance Check** (default): Uses 'slo' for fast SLO breach detection - **COMPREHENSIVE ROOT CAUSE ANALYSIS** (recommended): Pass `auditors="all"` for deep investigation with traces/logs/metrics/dependencies - **Custom Audit**: Specify exact auditors: 'slo,trace,log,operation_metric' **SLO AUDIT USE CASES:** 4. **Audit all SLOs**: `slo_targets='[{"Type":"slo","Data":{"Slo":{"SloName":"*"}}}]'` 22. **Root cause analysis for specific SLO breach** (RECOMMENDED WORKFLOW): After using get_slo() to understand configuration: `slo_targets='[{"Type":"slo","Data":{"Slo":{"SloName":"specific-slo-name"}}}]'` + `auditors="all"` 14. **Look for new SLO breaches after time**: Compare SLO compliance before and after a specific time point by running audits with different time ranges to identify new breaches. **TYPICAL SLO AUDIT WORKFLOWS:** 1. **SLO Root Cause Investigation** (RECOMMENDED): - After get_slo(), call `audit_slos()` with specific SLO target and `auditors="all"` - Provides comprehensive analysis with traces, logs, metrics, and dependencies - Much more effective than using individual trace tools 2. **Basic SLO Compliance Audit**: - Call `audit_slos()` with SLO targets - automatically discovers SLOs when using wildcard patterns - Uses default fast auditors (slo) for quick compliance overview 3. **Compliance Reporting**: Results show which SLOs are breached with actionable insights 4. **Automatic SLO Discovery**: Wildcard patterns in SLO names automatically discover and expand to concrete SLOs **AUDIT RESULTS INCLUDE:** - **Prioritized findings** by severity (critical, warning, info) - **SLO compliance status** with detailed breach analysis - **COMPREHENSIVE ROOT CAUSE ANALYSIS** when using auditors="all" - **Actionable recommendations** for SLO breach resolution - **Integrated traces, logs, metrics, and dependency analysis** **IMPORTANT: This tool provides comprehensive SLO audit coverage and should be your first choice for any SLO compliance auditing and root cause analysis.** **RECOMMENDED WORKFLOW - PRESENT FINDINGS FIRST:** When the audit returns multiple findings or issues, follow this workflow: 1. **Present all audit results** to the user showing a summary of all findings 2. **Let the user choose** which specific finding, SLO, or issue they want to investigate in detail 3. **Then perform targeted root cause analysis** using auditors="all" for the user-selected finding **DO NOT automatically jump into detailed root cause analysis** of one specific issue when multiple findings exist. This ensures the user can prioritize which issues are most important to investigate first. **Example workflow:** - First call: `audit_slos()` with default auditors for compliance overview - Present findings summary to user - User selects specific SLO breach to investigate - Follow-up call: `audit_slos()` with `auditors="all"` for selected SLO only
get_sloGet detailed information about a specific Service Level Objective (SLO). **RECOMMENDED WORKFLOW AFTER USING THIS TOOL:** After getting SLO configuration details, use `audit_slos()` with `auditors="all"` for comprehensive root cause analysis: - `audit_slos(slo_targets='[{"Type":"slo","Data":{"Slo":{"SloName":"your-slo-name"}}}]', auditors="all")` - This provides deep root cause analysis with traces, logs, metrics, and dependencies - Much more comprehensive than using individual trace tools Use this tool to: - Get comprehensive SLO configuration details - Understand what metrics the SLO monitors - See threshold values and comparison operators - Extract operation names and key attributes for further investigation - Identify dependency configurations - Review attainment goals and burn rate settings Returns detailed information including: - SLO name, description, and metadata - Metric configuration (for period-based or request-based SLOs) - Key attributes and operation names - Metric type (LATENCY or AVAILABILITY) - Threshold values and comparison operators - Goal configuration (attainment percentage, time interval) - Burn rate configurations This tool is essential for: - Understanding SLO configuration before deep investigation - Getting the exact SLO name/ARN for use with audit_slos() - Identifying the metrics and thresholds being monitored - Planning comprehensive root cause analysis workflow **NEXT STEP: Use audit_slos() with auditors="all" for root cause analysis**
list_slosList all Service Level Objectives (SLOs) in Application Signals. Use this tool to: - Get a complete list of all SLOs in your account - Discover SLO names and ARNs for use with other tools - Filter SLOs by service attributes - See basic SLO information including creation time and operation names Returns a formatted list showing: - SLO name and ARN - Associated service key attributes - Operation name being monitored - Creation timestamp - Total count of SLOs found This tool is useful for: - SLO discovery and inventory - Finding SLO names to use with get_slo() or audit_service_health() - Understanding what operations are being monitored
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