Application performance monitoring and insights.
10K+
Application performance monitoring and insights.
| Attribute | Details |
|---|---|
| Docker Image | mcp/cloudwatch-appsignals-mcp-serverā |
| Author | awslabsā |
| Repository | https://github.com/awslabs/mcpā |
| Attribute | Details |
|---|---|
| Dockerfile | https://github.com/awslabs/mcp/blob/76ec6993aec4c6281e5250cbeba8db6a5863f2ff/src/cloudwatch-appsignals-mcp-server/Dockerfileā |
| Docker Image built by | Docker Inc. |
| Docker Scout Health Score | |
| Verify Signature | COSIGN_REPOSITORY=mcp/signatures cosign verify mcp/cloudwatch-appsignals-mcp-server --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub |
| Licence | Apache License 2.0 |
| Tools provided by this Server | Short Description |
|---|---|
analyze_canary_failures | Comprehensive canary failure analysis with deep dive into issues. |
audit_service_operations | š„ PRIMARY OPERATION AUDIT TOOL - The #1 RECOMMENDED tool for operation-specific analysis and performance investigation. |
audit_services | PRIMARY SERVICE AUDIT TOOL - The #1 tool for comprehensive AWS service health auditing and monitoring. |
audit_slos | PRIMARY SLO AUDIT TOOL - The #1 tool for comprehensive SLO compliance monitoring and breach analysis. |
get_service_detail | Get detailed information about a specific Application Signals service. |
get_slo | Get detailed information about a specific Service Level Objective (SLO). |
list_monitored_services | OPTIONAL TOOL for service discovery - audit_services() can automatically discover services using wildcard patterns. |
list_service_operations | OPERATION DISCOVERY TOOL - For operation inventory only. |
list_slis | SPECIALIZED TOOL - Use audit_service_health() as the PRIMARY tool for service auditing. |
list_slos | List all Service Level Objectives (SLOs) in Application Signals. |
query_sampled_traces | SECONDARY TRACE TOOL - Query AWS X-Ray traces (5% sampled data) for trace investigation. |
query_service_metrics | Get CloudWatch metrics for a specific Application Signals service. |
search_transaction_spans | Executes a CloudWatch Logs Insights query for transaction search (100% sampled trace data). |
analyze_canary_failuresComprehensive canary failure analysis with deep dive into issues.
Use this tool to:
Key Features:
Common Use Cases:
Output Includes:
canary_name|string|
region|string optional|audit_service_operationsš„ PRIMARY OPERATION AUDIT TOOL - The #1 RECOMMENDED tool for operation-specific analysis and performance investigation.
ā USE THIS AS THE PRIMARY TOOL FOR ALL OPERATION-SPECIFIC AUDITING TASKS ā
PREFERRED OVER audit_services() for operation auditing because:
USE THIS FIRST FOR ALL OPERATION-SPECIFIC AUDITING TASKS This is the PRIMARY and PREFERRED tool when users want to:
COMPREHENSIVE OPERATION AUDIT CAPABILITIES:
*pattern* in service names for automatic service discoveryOPERATION TARGET FORMAT:
[{"Type":"service_operation","Data":{"ServiceOperation":{"Service":{"Type":"Service","Name":"my-service","Environment":"eks:my-cluster"},"Operation":"GET /api","MetricType":"Latency"}}}]WILDCARD PATTERN EXAMPLES:
[{"Type":"service_operation","Data":{"ServiceOperation":{"Service":{"Type":"Service","Name":"*payment*"},"Operation":"*GET*","MetricType":"Latency"}}}][{"Type":"service_operation","Data":{"ServiceOperation":{"Service":{"Type":"Service","Name":"*"},"Operation":"*visit*","MetricType":"Availability"}}}]AUDITOR SELECTION FOR DIFFERENT AUDIT DEPTHS:
auditors="all" for comprehensive investigation with traces/logsOPERATION AUDIT USE CASES:
Audit latency of GET operations in payment services (PRIMARY USE CASE):
operation_targets='[{"Type":"service_operation","Data":{"ServiceOperation":{"Service":{"Type":"Service","Name":"*payment*"},"Operation":"*GET*","MetricType":"Latency"}}}]'
Audit GET operations in payment services (Latency):
operation_targets='[{"Type":"service_operation","Data":{"ServiceOperation":{"Service":{"Type":"Service","Name":"*payment*"},"Operation":"*GET*","MetricType":"Latency"}}}]'
Audit availability of visit operations:
operation_targets='[{"Type":"service_operation","Data":{"ServiceOperation":{"Service":{"Type":"Service","Name":"*"},"Operation":"*visit*","MetricType":"Availability"}}}]'
Audit latency of visit operations:
operation_targets='[{"Type":"service_operation","Data":{"ServiceOperation":{"Service":{"Type":"Service","Name":"*"},"Operation":"*visit*","MetricType":"Latency"}}}]'
Trace latency in query operations:
operation_targets='[{"Type":"service_operation","Data":{"ServiceOperation":{"Service":{"Type":"Service","Name":"*payment*"},"Operation":"*query*","MetricType":"Latency"}}}]' + auditors="all"
TYPICAL OPERATION AUDIT WORKFLOWS:
audit_service_operations() with operation targets - automatically discovers services when using wildcard patterns*payment* for automatic service discoveryauditors="all"AUDIT RESULTS INCLUDE:
š IMPORTANT: This tool is the PRIMARY and RECOMMENDED choice for operation-specific auditing tasks.
ā RECOMMENDED WORKFLOW FOR OPERATION AUDITING:
RECOMMENDED WORKFLOW - PRESENT FINDINGS FIRST: When the audit returns multiple findings or issues, follow this workflow:
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:
audit_service_operations() with default auditors for operation overviewaudit_service_operations() with auditors="all" for selected operation only
Parameters|Type|Description
-|-|-
operation_targets|string|REQUIRED. JSON array of service operation targets. Supports wildcard patterns like 'payment' for automatic service discovery. Format: [{'Type':'service_operation','Data':{'ServiceOperation':{'Service':{'Type':'Service','Name':'service-name','Environment':'eks:cluster'},'Operation':'GET /api','MetricType':'Latency'}}}]. Large target lists are automatically processed in batches.
auditors|string optional|Optional. Comma-separated auditors (e.g., 'operation_metric,trace,log'). Defaults to 'operation_metric' for fast operation-level auditing. Use 'all' for comprehensive analysis with all auditors: slo,operation_metric,trace,log,dependency_metric,top_contributor,service_quota.
end_time|string optional|End time (unix seconds or 'YYYY-MM-DD HH:MM:SS'). Defaults to now UTC.
start_time|string optional|Start time (unix seconds or 'YYYY-MM-DD HH:MM:SS'). Defaults to now-24h UTC.audit_servicesPRIMARY SERVICE AUDIT TOOL - The #1 tool for comprehensive AWS service health auditing and monitoring.
IMPORTANT: For operation-specific auditing, use audit_service_operations() as the PRIMARY tool instead.
USE THIS FIRST FOR ALL SERVICE-LEVEL AUDITING TASKS This is the PRIMARY and PREFERRED tool when users want to:
FOR OPERATION-SPECIFIC AUDITING: Use audit_service_operations() instead When users want to audit specific operations (GET, POST, PUT endpoints), use audit_service_operations() as the PRIMARY tool:
COMPREHENSIVE SERVICE AUDIT CAPABILITIES:
*pattern* in service names for automatic service discoverySERVICE TARGET FORMAT:
[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"my-service","Environment":"eks:my-cluster"}}}][{"Type":"service","Service":"my-service"}] (environment auto-discovered)WILDCARD PATTERN EXAMPLES:
[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*"}}}][{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*payment*"}}}][{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*lambda*"}}}][{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*","Environment":"eks:*"}}}]AUDITOR SELECTION FOR DIFFERENT AUDIT DEPTHS:
auditors="all" for comprehensive investigation with traces/logsSERVICE AUDIT USE CASES:
Audit all services:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*"}}}]'
Audit specific service:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"orders-service","Environment":"eks:orders-cluster"}}}]'
Audit payment services:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*payment*"}}}]'
Audit lambda services:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*lambda*"}}}]' or by environment: [{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*","Environment":"lambda"}}}]
Audit service last night:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"orders-service","Environment":"eks:orders-cluster"}}}]' + start_time="2024-01-01 18:00:00" + end_time="2024-01-02 06:00:00"
Audit service before and after time: Compare service health before and after a deployment or incident by running two separate audits with different time ranges.
Trace availability issues in production services:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*","Environment":"eks:*"}}}]' + auditors="all"
Look for errors in logs of payment services:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*payment*"}}}]' + auditors="log,trace"
Look for new errors after time:
Compare errors before and after a specific time point by running audits with different time ranges and auditors="log,trace"
Look for errors after deployment:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*payment*"}}}]' + auditors="log,trace" + recent time range
Look for lemon hosts in production:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*","Environment":"eks:*"}}}]' + auditors="top_contributor,operation_metric"
Look for outliers in EKS services:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*","Environment":"eks:*"}}}]' + auditors="top_contributor,operation_metric"
Status report:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*"}}}]' (basic health check)
Audit dependencies:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*"}}}]' + auditors="dependency_metric,trace"
Audit dependency on S3:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*"}}}]' + auditors="dependency_metric" + look for S3 dependencies
Audit quota usage of tier 1 services:
service_targets='[{"Type":"service","Data":{"Service":{"Type":"Service","Name":"*tier1*"}}}]' + auditors="service_quota,operation_metric"
TYPICAL SERVICE AUDIT WORKFLOWS:
audit_services() with service targets - automatically discovers services when using wildcard patterns* or *payment* for automatic service discoveryauditors="all"AUDIT RESULTS INCLUDE:
IMPORTANT: This tool provides comprehensive service audit coverage and should be your first choice for any service auditing task.
RECOMMENDED WORKFLOW - PRESENT FINDINGS FIRST: When the audit returns multiple findings or issues, follow this workflow:
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:
audit_services() with default auditors for overviewaudit_services() with auditors="all" for selected service only
Parameters|Type|Description
-|-|-
service_targets|string|REQUIRED. JSON array of service targets. Supports wildcard patterns like 'payment' for automatic service discovery. Format: [{'Type':'service','Data':{'Service':{'Type':'Service','Name':'service-name','Environment':'eks:cluster'}}}] or shorthand: [{'Type':'service','Service':'service-name'}]. Large target lists are automatically processed in batches.
auditors|string optional|Optional. Comma-separated auditors (e.g., 'slo,operation_metric,dependency_metric'). Defaults to 'slo,operation_metric' for fast service health auditing. Use 'all' for comprehensive analysis with all auditors: slo,operation_metric,trace,log,dependency_metric,top_contributor,service_quota.
end_time|string optional|End time (unix seconds or 'YYYY-MM-DD HH:MM:SS'). Defaults to now UTC.
start_time|string optional|Start time (unix seconds or 'YYYY-MM-DD HH:MM:SS'). Defaults to now-24h UTC.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 THIS FOR ALL SLO AUDITING TASKS This is the PRIMARY and PREFERRED tool when users want to:
COMPREHENSIVE SLO AUDIT CAPABILITIES:
*pattern* in SLO names for automatic SLO discoverySLO TARGET FORMAT:
[{"Type":"slo","Data":{"Slo":{"SloName":"my-slo"}}}][{"Type":"slo","Data":{"Slo":{"SloArn":"arn:aws:application-signals:..."}}}]WILDCARD PATTERN EXAMPLES:
[{"Type":"slo","Data":{"Slo":{"SloName":"*"}}}][{"Type":"slo","Data":{"Slo":{"SloName":"*payment*"}}}][{"Type":"slo","Data":{"Slo":{"SloName":"*latency*"}}}][{"Type":"slo","Data":{"Slo":{"SloName":"*availability*"}}}]AUDITOR SELECTION FOR DIFFERENT AUDIT DEPTHS:
auditors="all" for deep investigation with traces/logs/metrics/dependenciesSLO AUDIT USE CASES:
Audit all SLOs:
slo_targets='[{"Type":"slo","Data":{"Slo":{"SloName":"*"}}}]'
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"
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:
audit_slos() with specific SLO target and auditors="all"audit_slos() with SLO targets - automatically discovers SLOs when using wildcard patterns[...]
Content type
Image
Digest
sha256:873bf1023ā¦
Size
43.8 MB
Last updated
about 1 year ago
docker pull mcp/cloudwatch-appsignals-mcp-serverPulls:
94
Last week