aws-observability

Configure and debug AWS observability across CloudWatch, X-Ray, CloudTrail, and ADOT instrumentation.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill aws-observability-sakicodes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-observability
Source: https://github.com/sakicodes/BuildFestHackathon26/tree/main/.agents/skills/aws-observability
Command: npx skills add https://github.com/sakicodes/BuildFestHackathon26 --skill aws-observability-sakicodes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Setting up and operating AWS observability involves dozens of services with subtle constraints — alarm evaluation mechanics, EMF limits, X-Ray sampling rules, and ADOT auto-instrumentation steps — that are easy to misconfigure. This Skill provides domain expertise for building, debugging, and optimizing the full observability stack, including onboarding un-instrumented services to Application Signals. ## Core Features & Use Cases - Application Signals Onboarding: Enable ADOT auto-instrumentation on EC2, ECS, EKS, and Lambda for Python, Node.js, Java, and .NET, including ServiceEvents metadata, OTLP endpoints, and Dynamic Instrumentation. - CloudWatch Operations: Write Log Insights queries, configure metric/composite/anomaly alarms with best-practice defaults, publish custom metrics via EMF, and build dashboards. - Tracing & Auditing: Migrate from X-Ray SDK to ADOT, tune sampling rules, and perform CloudTrail operational auditing. - Use Case: A DevOps engineer needs to onboard a Python service on EKS to Application Signals and add error-rate alarms. The Skill guides the EKS add-on setup, IAM policies, inject annotations, and provides a CDK alarm template with p99 latency and M-of-N evaluation defaults. ## Quick Start Ask the assistant to enable Application Signals on your EKS Python service or to create a CloudWatch alarm for Lambda errors using best-practice defaults.

Frequently Asked Questions about aws-observability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable Application Signals on an EKS service?

Install the amazon-cloudwatch-observability EKS add-on, attach CloudWatchAgentServerPolicy and AWSXRayDaemonWriteAccess to the node role, then apply the ADOT inject annotation for your language. The Skill provides per-language guides for Python, Node.js, Java, and .NET.

How do I create a CloudWatch alarm for Lambda errors?

Alarm on error rate using a math expression (errors * 100 / invocations) rather than raw error counts. Use evaluationPeriods of 3, datapointsToAlarm of 2, a 60-second period, and treatMissingData set to notBreaching.

Should I use X-Ray SDK or ADOT for new projects?

Use ADOT (OpenTelemetry) for all new projects. The X-Ray SDK is in maintenance mode, while ADOT is actively developed, vendor-neutral, and supports multiple backends including CloudWatch, X-Ray, and Prometheus.

Why is my CloudWatch alarm stuck in INSUFFICIENT_DATA?

The namespace or dimension names likely do not match exactly, or the metric is not being published. Verify the exact namespace (case-sensitive) and dimensions, and check the missing data treatment setting on the alarm.

Does Application Signals ServiceEvents work on Lambda or .NET?

No. ServiceEvents (git/deployment metadata, OTLP endpoints, Dynamic Instrumentation) is supported only on EC2, ECS, and EKS with Python, Node.js, or Java. Lambda and .NET services get Tier 1 Application Signals enablement only.

What are the limits of CloudWatch Logs Insights queries?

Queries support a maximum of 50 log groups, 100 concurrent queries per account, and a 60-minute timeout. The pattern, diff, unmask, anomaly, and filterIndex commands do not work on Infrequent Access log class.