skills.rest
dennisvink
dennisvinkCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

aws-observability

Configures and debugs AWS observability across CloudWatch, X-Ray, CloudTrail, and ADOT instrumentation.

Updated Sep 8, 2026
Search Tags:#aws#observability#opentelemetry#cloudwatch#alarms#x-ray#application signals
One-click install
npx skills add https://github.com/dennisvink/yolomancer --skill aws-observability-dennisvink
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aws-observability
Source: https://github.com/dennisvink/yolomancer/tree/main/skills/aws/core-skills/aws-observability
Command: npx skills add https://github.com/dennisvink/yolomancer --skill aws-observability-dennisvink

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires boto3, botocore, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Setting up and troubleshooting AWS observability requires deep knowledge of CloudWatch alarms, Log Insights queries, X-Ray tracing, ADOT collectors, and Application Signals onboarding, with many subtle defaults and constraints that cause misconfigurations. ## Core Features & Use Cases - Application Signals Onboarding: Enable auto-instrumentation for services on EC2, ECS, EKS, and Lambda in Python, Node.js, Java, and .NET using ADOT SDKs, including ServiceEvents metadata propagation through CI/CD pipelines. - CloudWatch Configuration: Build metric, composite, and anomaly detection alarms with recommended defaults, write Log Insights queries, publish custom metrics via EMF, and design dashboards with cross-account support. - Dynamic Instrumentation: Debug live running services with breakpoints and snapshot capture without redeploying code, using dedicated Python scripts for instrumentation CRUD operations. - Use Case: A team needs to onboard a Python service on EKS to Application Signals, add deployment metadata env vars to their GitHub Actions workflow, and create p99 latency alarms with a CDK dashboard template. ## Quick Start Ask the assistant to enable Application Signals auto-instrumentation for your service, or to write a CloudWatch alarm or Log Insights query for your workload.

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 for a service on EKS?▼

Install the amazon-cloudwatch-observability EKS add-on, attach CloudWatchAgentServerPolicy and AWSXRayDaemonWriteAccess to the node group role, then apply the per-language inject annotation from the matching platform-language guide. ServiceEvents extras require add-on v6.3.0 or later.

How do I create a CloudWatch alarm for Lambda error rate?▼

Use a metric math expression dividing Errors by Invocations rather than raw error counts, with evaluationPeriods of 3, datapointsToAlarm of 2, and treatMissingData set to notBreaching. A CDK template implementing these defaults is included in the assets directory.

Does Application Signals onboarding support Lambda and .NET?▼

Lambda and .NET support Tier 1 Application Signals enablement only. ServiceEvents features like git metadata env vars, OTLP endpoints, and Dynamic Instrumentation are limited to EC2, ECS, and EKS running Python, Node.js, or Java.

Why does my CloudWatch alarm fire later than expected?▼

CloudWatch evaluates alarms over a wider lookback window than the configured evaluation periods, and alarms with evaluation windows over one day are evaluated only once per hour. Dead man switch alarms with multi-day periods can take days longer than expected to trigger.

Can I debug a running service without redeploying code?▼

Yes, Dynamic Instrumentation lets you place breakpoints and probes on live services to capture arguments, locals, return values, and stack traces as snapshots. It requires the Dynamic Instrumentation env var enabled and works on EC2, ECS, and EKS with Python, Node.js, or Java.

What are the limitations of composite CloudWatch alarms?▼

Composite alarms cannot perform EC2 actions like stop or terminate, nor Auto Scaling actions. They and all underlying alarms must be in the same account and Region, with a maximum of 100 underlying alarms per composite.

Related Skills

Explore More Software Engineering Skills→
Lobbi-DocsLobbi-Docs
18

aws

Automate AWS infrastructure provisioning and management across EC2, EKS, S3, Lambda, RDS, and IAM.

Official
Advanced
n4vyshn4vysh
5

aws-observability

Automate AWS observability workflows with CloudWatch, X-Ray, CloudTrail, and ADOT.

Community
Advanced
xlelibertyxleliberty

deploy

Analyze codebases and generate secure AWS Infrastructure as Code.

Community
Advanced
tense-itense-i
1

opentelemetry

Deploy OpenTelemetry Collector via Helm and configure telemetry pipelines in Kubernetes.

Community
Advanced