create-observability-config

Name: create-observability-config
Availability: InStock
Author: foolishimp

Generate per-REQ dashboards and alerts for Datadog, Prometheus, and Splunk.

Updated Aug 27, 2026

Search Tags:#monitoring #dashboards #observability #prometheus #datadog #sla #splunk

Ready to run

npx skills add https://github.com/foolishimp/ai_sdlc_method --skill create-observability-config

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-observability-config
Source: https://github.com/foolishimp/ai_sdlc_method/tree/main/gemini-code/plugins/runtime-skills/skills/create-observability-config
Command: npx skills add https://github.com/foolishimp/ai_sdlc_method --skill create-observability-config

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill configures production-grade observability by generating per-REQ dashboards and alerts across Datadog, Prometheus, and Splunk, enabling SLA tracking and faster incident detection.

Core Features & Use Cases

Per-Requirement Dashboards: Create dashboards for each REQ-* to monitor success rate, latency, and errors.
Alerts & SLA Tracking: Provision monitors for SLA violations and automatic alerting.
Unified Telemetry: Centralize log aggregation and trace visualization filtered by REQ-* tags.
Use Case: Before going live, auto-provision observability artifacts for all requirements to reduce setup time from days to minutes.

Quick Start

Use this skill to set up observability for your deployment by generating dashboards and monitors for all requirements (REQ-001, REQ-002, ...). This will provision the Datadog/Prometheus/Splunk artifacts with minimal manual steps.

Frequently Asked Questions about create-observability-config

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

FAQPage Schema

How do I automate observability dashboards for each requirement during deployment?▼

Automate observability dashboards by using this Skill to generate per-REQ dashboards and alerts across Datadog, Prometheus, and Splunk during production deployment. It provisions monitoring artifacts for each REQ-* identifier, reducing setup time from days to minutes and enabling immediate SLA tracking and incident detection.

Can I track SLA violations and latency across multiple monitoring platforms?▼

Yes. This Skill provisions unified SLA monitoring and latency tracking by creating alerts and dashboards simultaneously across Datadog, Prometheus, and Splunk, filtering by REQ-* tags to centralize telemetry and enable cross-platform tracing.

What's the best way to set up per-requirement log aggregation and trace visualization?▼

Configure per-requirement log aggregation and trace visualization by using this Skill to generate centralized filtering rules tagged by REQ-* across your observability stack. It automatically provisions log aggregation and trace visualization endpoints for each requirement across Datadog, Prometheus, and Splunk.

Do I need to manually create dashboards and monitors for each requirement before going live?▼

No. This Skill eliminates manual dashboard and monitor creation by auto-provisioning observability artifacts for all REQ-* identifiers before deployment, generating dashboards, alerts, and log filters across Datadog, Prometheus, and Splunk in a single operation.

How does per-REQ observability configuration reduce incident detection time?▼

Per-REQ observability configuration accelerates incident detection by automatically creating dedicated dashboards and alerts for each requirement, enabling real-time success rate and error tracking filtered by REQ-* tags. This eliminates manual log and trace filtering during incidents.

Can this work if I'm using only one monitoring platform instead of all three?▼

Yes. This Skill provisions observability artifacts for Datadog, Prometheus, and Splunk independently, allowing you to generate per-REQ dashboards and alerts for whichever platforms are in your deployment environment.