@nockdev/awf 6.2.0

package/.agent/skills/core/observability/META.yaml

@@ -0,0 +1,76 @@
+name: observability
+version: "6.2.0"
+display: Observability Patterns
+category: core
+tier: 1
+priority: 0
+
+desc: "Comprehensive observability patterns for metrics, tracing, and profiling. Covers OpenTelemetry, Prometheus, Jaeger, and 12 programming languages."
+
+triggers:
+  file_patterns: []
+  keywords:
+    - observability
+    - metrics
+    - tracing
+    - monitoring
+    - prometheus
+    - opentelemetry
+    - otel
+    - grafana
+    - jaeger
+    - profiling
+    - spans
+    - SLO
+    - SLI
+    - alerting
+    - RED method
+    - USE method
+    - pprof
+  intents:
+    - setup monitoring
+    - add metrics
+    - distributed tracing
+    - observability stack
+
+caps:
+  - Metrics collection patterns (Prometheus, StatsD)
+  - Distributed tracing (OpenTelemetry, Jaeger, Zipkin)
+  - Profiling (CPU, memory, continuous)
+  - Alerting and SLO-based monitoring
+  - Dashboard design patterns
+  - Anti-patterns detection
+
+hsa:
+  enabled: true
+  adapter: observability_adapter.py
+  functions:
+    - search_observability_patterns
+    - get_metrics_patterns
+    - get_tracing_patterns
+    - get_otel_patterns
+    - get_language_patterns
+    - get_alerting_patterns
+    - get_profiling_patterns
+
+data_files:
+  - data/core-patterns.yaml
+  - data/otel-core.yaml
+  - data/metrics-prometheus.yaml
+  - data/metrics-patterns.yaml
+  - data/tracing-patterns.yaml
+  - data/tracing-tools.yaml
+  - data/profiling-patterns.yaml
+  - data/alerting-patterns.yaml
+  - data/language-go.yaml
+  - data/language-python.yaml
+  - data/language-typescript.yaml
+  - data/language-rust.yaml
+  - data/language-java.yaml
+  - data/language-csharp.yaml
+  - data/language-cpp.yaml
+  - data/language-others.yaml
+  - data/anti-patterns.yaml
+
+related_skills:
+  - logging

package/.agent/skills/core/observability/SKILL.md

@@ -0,0 +1,153 @@
+# 🔭 Observability Skill v1.0
+
+> **400+ Patterns** | **12 Languages** | **OpenTelemetry Standard**
+
+---
+
+## Quick Stats
+
+| Metric      | Value                    |
+| ----------- | ------------------------ |
+| Patterns    | 400+                     |
+| Languages   | 12                       |
+| Categories  | 8                        |
+| HSA Adapter | ✅ observability_adapter |
+
+---
+
+## Three Pillars + Profiling
+
+| Pillar        | Purpose                      | Tools                          |
+| ------------- | ---------------------------- | ------------------------------ |
+| **Metrics**   | Numerical trends, alerts     | Prometheus, Micrometer, StatsD |
+| **Tracing**   | Request flow                 | OpenTelemetry, Jaeger, Zipkin  |
+| **Logs**      | Events (see `logging` skill) | -                              |
+| **Profiling** | CPU/Memory hotspots          | pprof, Valgrind, Tracy         |
+
+---
+
+## Language Coverage
+
+| Language   | Libraries                         | Patterns |
+| ---------- | --------------------------------- | -------- |
+| Go         | otel-go, pprof, prometheus-go     | 25       |
+| Python     | otel-python, prometheus_client    | 25       |
+| TypeScript | otel-js, prom-client, dd-trace    | 25       |
+| Rust       | tracing, opentelemetry-rust       | 25       |
+| Java       | Micrometer, Spring Actuator       | 25       |
+| C#         | DiagnosticSource, AppInsights     | 25       |
+| C++        | prometheus-cpp, Tracy, Valgrind   | 25       |
+| Swift      | MetricKit, otel-swift             | 15       |
+| Kotlin     | Firebase Performance, otel-kotlin | 15       |
+| Others     | PHP, Ruby, Elixir                 | 15       |
+
+---
+
+## Core Patterns
+
+### OpenTelemetry
+
+```yaml
+otel-core:
+  - SDK initialization
+  - TracerProvider setup
+  - MeterProvider setup
+  - OTLP exporter configuration
+  - Context propagation
+  - Semantic conventions
+  - Auto-instrumentation
+  - Manual instrumentation
+```
+
+### Metrics (RED/USE Methods)
+
+```yaml
+metrics-patterns:
+  RED: # Request-oriented
+    - Rate (requests/sec)
+    - Errors (rate)
+    - Duration (latency)
+  USE: # Resource-oriented
+    - Utilization (%)
+    - Saturation (queue depth)
+    - Errors (count)
+```
+
+### Tracing
+
+```yaml
+tracing-patterns:
+  - Span creation
+  - Context propagation
+  - Sampling strategies (head/tail)
+  - Baggage items
+  - Error recording
+  - Span links
+```
+
+### Alerting
+
+```yaml
+alerting-patterns:
+  - SLO-based alerts
+  - Multi-window burn rate
+  - Error budget policies
+  - On-call best practices
+  - Alert fatigue prevention
+```
+
+---
+
+## HSA Integration
+
+### Available Functions
+
+```python
+# General search
+search_observability_patterns("prometheus go metrics", top_k=10)
+
+# Category-specific
+get_metrics_patterns()
+get_tracing_patterns()
+get_otel_patterns(signal="traces")  # traces|metrics|logs
+get_profiling_patterns()
+get_alerting_patterns()
+
+# Language-specific
+get_language_patterns("go")     # 25 patterns
+get_language_patterns("rust")   # 25 patterns
+get_language_patterns("cpp")    # 25 patterns
+```
+
+---
+
+## Data Files (16 CSVs)
+
+| Category  | File                   | Patterns |
+| --------- | ---------------------- | -------- |
+| Core      | core-patterns.csv      | 30       |
+| Core      | otel-core.csv          | 30       |
+| Metrics   | metrics-prometheus.csv | 25       |
+| Metrics   | metrics-patterns.csv   | 20       |
+| Tracing   | tracing-patterns.csv   | 25       |
+| Tracing   | tracing-tools.csv      | 20       |
+| Profiling | profiling-patterns.csv | 20       |
+| Alerting  | alerting-patterns.csv  | 25       |
+| Languages | language-\*.csv        | 220      |
+| Anti      | anti-patterns.csv      | 15       |
+| **Total** | -                      | **~400** |
+
+---
+
+## Anti-Patterns
+
+| Anti-Pattern            | Why Bad          | Fix                    |
+| ----------------------- | ---------------- | ---------------------- |
+| High cardinality labels | Memory explosion | Bound label values     |
+| Too many dashboards     | Alert fatigue    | SLO-focused dashboards |
+| Metrics without alerts  | Invisible issues | Define thresholds      |
+| Traces without context  | Hard debugging   | Add correlation IDs    |
+
+---
+
+_DOMYH Awesome Code • Observability • OpenTelemetry Standard_

package/.agent/skills/core/observability/data/alerting-patterns.yaml

@@ -0,0 +1,165 @@
+metadata:
+  skill: observability
+  domain: alerting_patterns
+  version: 6.2.0
+  updated: '2026-02-05'
+  migrated_from: alerting-patterns.csv
+  patterns_count: 25
+  columns:
+  - pattern_id
+  - name
+  - category
+  - description
+  - example
+  - level
+patterns:
+- id: ALT-001
+  name: SLO-Based Alerts
+  category: Alerting
+  description: Alert on SLO violations
+  example: Error budget burn rate
+  level: intermediate
+- id: ALT-002
+  name: Multi-Window Burn Rate
+  category: Alerting
+  description: Short + long window alerts
+  example: 1h=14x OR 6h=6x burn rate
+  level: advanced
+- id: ALT-003
+  name: Error Budget Alerts
+  category: Alerting
+  description: Alert when budget consumed
+  example: 50% budget used = warning
+  level: intermediate
+- id: ALT-004
+  name: Symptom-Based Alerts
+  category: Alerting
+  description: Alert on user impact
+  example: Latency > SLO target
+  level: intermediate
+- id: ALT-005
+  name: Cause-Based Alerts
+  category: Alerting
+  description: Alert on underlying issues
+  example: CPU > 90% (less recommended)
+  level: intermediate
+- id: ALT-006
+  name: Alert Severity Levels
+  category: Alerting
+  description: P1/P2/P3/P4 classification
+  example: P1 = page, P4 = ticket
+  level: beginner
+- id: ALT-007
+  name: Alert Routing
+  category: Alerting
+  description: Send to right channel
+  example: Slack for low, PagerDuty for high
+  level: intermediate
+- id: ALT-008
+  name: Alert Grouping
+  category: Alerting
+  description: Combine related alerts
+  example: Group by service + severity
+  level: intermediate
+- id: ALT-009
+  name: Alert Silencing
+  category: Alerting
+  description: Suppress during maintenance
+  example: Silence for 1h during deploy
+  level: beginner
+- id: ALT-010
+  name: Alert Inhibition
+  category: Alerting
+  description: Suppress child alerts
+  example: If cluster down, suppress pod alerts
+  level: advanced
+- id: ALT-011
+  name: Alert Fatigue
+  category: Alerting
+  description: Too many alerts desensitize
+  example: Reduce noise, focus on actionable
+  level: intermediate
+- id: ALT-012
+  name: Runbook Links
+  category: Alerting
+  description: Include remediation steps
+  example: Each alert links to runbook
+  level: beginner
+- id: ALT-013
+  name: Alert Testing
+  category: Alerting
+  description: Verify alerts fire correctly
+  example: Synthetic failures, chaos testing
+  level: intermediate
+- id: ALT-014
+  name: On-Call Practices
+  category: Alerting
+  description: Rotation, escalation, handoff
+  example: Clear rotation schedule
+  level: intermediate
+- id: ALT-015
+  name: Incident Levels
+  category: Alerting
+  description: SEV1/SEV2/SEV3 classification
+  example: SEV1 = customer impact
+  level: intermediate
+- id: ALT-016
+  name: Post-Incident Review
+  category: Alerting
+  description: Blameless retrospectives
+  example: Focus on systems not people
+  level: intermediate
+- id: ALT-017
+  name: Alert-to-Incident
+  category: Alerting
+  description: When to create incidents
+  example: Multiple alerts = incident
+  level: beginner
+- id: ALT-018
+  name: Dashboard Alerts
+  category: Alerting
+  description: Visual alert status
+  example: Red/yellow/green indicators
+  level: beginner
+- id: ALT-019
+  name: Threshold Tuning
+  category: Alerting
+  description: Adjust alert thresholds
+  example: Analyze historical data
+  level: intermediate
+- id: ALT-020
+  name: Alert as Code
+  category: Alerting
+  description: Version control alert rules
+  example: Terraform, Jsonnet, YAML
+  level: intermediate
+- id: ALT-021
+  name: Dead Man's Switch
+  category: Alerting
+  description: Alert if no data received
+  example: Heartbeat monitoring
+  level: intermediate
+- id: ALT-022
+  name: Anomaly Alerts
+  category: Alerting
+  description: ML-based threshold detection
+  example: Dynamic baseline comparison
+  level: advanced
+- id: ALT-023
+  name: Composite Alerts
+  category: Alerting
+  description: Multiple conditions combined
+  example: A AND B OR C
+  level: advanced
+- id: ALT-024
+  name: Alert Deduplication
+  category: Alerting
+  description: Prevent duplicate pages
+  example: Dedupe by fingerprint
+  level: intermediate
+- id: ALT-025
+  name: Alert History
+  category: Alerting
+  description: Track alert trends
+  example: Reduce repeat offenders
+  level: intermediate

package/.agent/skills/core/observability/data/anti-patterns.yaml

@@ -0,0 +1,105 @@
+metadata:
+  skill: observability
+  domain: anti_patterns
+  version: 6.2.0
+  updated: '2026-02-05'
+  migrated_from: anti-patterns.csv
+  patterns_count: 15
+  columns:
+  - pattern_id
+  - name
+  - category
+  - description
+  - impact
+  - fix
+patterns:
+- id: ANTI-001
+  name: High Cardinality Labels
+  category: Anti-Pattern
+  description: Using unbounded values as labels
+  impact: Memory explosion/query slowness
+  fix: Use bounded enum values or drop high-cardinality labels
+- id: ANTI-002
+  name: Metrics Without Alerts
+  category: Anti-Pattern
+  description: Collecting metrics without alerting
+  impact: Issues go unnoticed
+  fix: Define thresholds and alert rules for critical metrics
+- id: ANTI-003
+  name: Alert Fatigue
+  category: Anti-Pattern
+  description: Too many noisy alerts
+  impact: Team ignores real issues
+  fix: Tune thresholds and reduce false positives
+- id: ANTI-004
+  name: Trace Without Context
+  category: Anti-Pattern
+  description: Spans missing correlation IDs
+  impact: Hard to debug across services
+  fix: Add trace_id/span_id to logs
+- id: ANTI-005
+  name: Log Without Structure
+  category: Anti-Pattern
+  description: Unstructured plain text logs
+  impact: Hard to query and analyze
+  fix: Use JSON structured logging
+- id: ANTI-006
+  name: Sampling Too Aggressively
+  category: Anti-Pattern
+  description: Missing rare errors/events
+  impact: Cannot debug edge cases
+  fix: Use tail-based sampling for errors
+- id: ANTI-007
+  name: Dashboard Overload
+  category: Anti-Pattern
+  description: Too many dashboards/panels
+  impact: Information overload
+  fix: Focus on SLO-based dashboards
+- id: ANTI-008
+  name: Metric Name Inconsistency
+  category: Anti-Pattern
+  description: Inconsistent naming conventions
+  impact: Hard to find and correlate
+  fix: Follow naming conventions (snake_case/units)
+- id: ANTI-009
+  name: Ignoring Profiling
+  category: Anti-Pattern
+  description: Never profiling in production
+  impact: Miss performance issues
+  fix: Enable continuous profiling
+- id: ANTI-010
+  name: No Baseline
+  category: Anti-Pattern
+  description: No historical comparison
+  impact: Cannot detect anomalies
+  fix: Establish baseline metrics
+- id: ANTI-011
+  name: Over-Instrumentation
+  category: Anti-Pattern
+  description: Too many spans/metrics
+  impact: Performance overhead/cost
+  fix: Focus on critical paths
+- id: ANTI-012
+  name: Missing Service Maps
+  category: Anti-Pattern
+  description: No dependency visualization
+  impact: Hard to understand system
+  fix: Generate service maps from traces
+- id: ANTI-013
+  name: Single Point of Failure
+  category: Anti-Pattern
+  description: One observability backend
+  impact: Data loss if backend fails
+  fix: Multi-region/HA setup
+- id: ANTI-014
+  name: No Retention Policy
+  category: Anti-Pattern
+  description: Keeping data forever
+  impact: Storage costs explode
+  fix: Define retention by signal type
+- id: ANTI-015
+  name: Ignoring Cost
+  category: Anti-Pattern
+  description: Not monitoring observability cost
+  impact: Budget overrun
+  fix: Track ingestion volume and optimize

package/.agent/skills/core/observability/data/core-patterns.yaml

@@ -0,0 +1,195 @@
+metadata:
+  skill: observability
+  domain: core_patterns
+  version: 6.2.0
+  updated: '2026-02-05'
+  migrated_from: core-patterns.csv
+  patterns_count: 30
+  columns:
+  - pattern_id
+  - name
+  - category
+  - description
+  - example
+  - level
+patterns:
+- id: OBS-001
+  name: Three Pillars
+  category: Core
+  description: Observability = Metrics + Logs + Traces
+  example: Collect all three for full system insight
+  level: beginner
+- id: OBS-002
+  name: SLI Definition
+  category: Core
+  description: Service Level Indicator - measurable metric
+  example: Request latency p99 < 200ms
+  level: intermediate
+- id: OBS-003
+  name: SLO Definition
+  category: Core
+  description: Service Level Objective - target for SLI
+  example: 99.9% of requests complete < 200ms
+  level: intermediate
+- id: OBS-004
+  name: Error Budget
+  category: Core
+  description: Allowed failure rate from SLO
+  example: 100% - 99.9% = 0.1% error budget
+  level: intermediate
+- id: OBS-005
+  name: Cardinality
+  category: Core
+  description: Number of unique label combinations
+  example: Limit labels to prevent metric explosion
+  level: advanced
+- id: OBS-006
+  name: Instrumentation
+  category: Core
+  description: Adding observability code to apps
+  example: Add metrics/traces at key points
+  level: beginner
+- id: OBS-007
+  name: Auto vs Manual
+  category: Core
+  description: Automatic vs manual instrumentation
+  example: Use auto for common libraries, manual for custom
+  level: intermediate
+- id: OBS-008
+  name: Context Propagation
+  category: Core
+  description: Passing trace context between services
+  example: Use W3C TraceContext headers
+  level: intermediate
+- id: OBS-009
+  name: Correlation IDs
+  category: Core
+  description: Unique ID linking related events
+  example: 'request_id: uuid in logs, traces, metrics'
+  level: beginner
+- id: OBS-010
+  name: Data Retention
+  category: Core
+  description: How long to keep observability data
+  example: 'Metrics: 30d, Traces: 7d, Logs: 90d'
+  level: intermediate
+- id: OBS-011
+  name: Sampling
+  category: Core
+  description: Collecting subset of data
+  example: 1% sample rate for high-traffic endpoints
+  level: advanced
+- id: OBS-012
+  name: Head-based Sampling
+  category: Core
+  description: Decide to sample at trace start
+  example: Deterministic based on trace ID
+  level: intermediate
+- id: OBS-013
+  name: Tail-based Sampling
+  category: Core
+  description: Decide after trace completes
+  example: Sample errors and slow requests
+  level: advanced
+- id: OBS-014
+  name: Semantic Conventions
+  category: Core
+  description: Standardized naming for telemetry
+  example: http.method, http.status_code
+  level: intermediate
+- id: OBS-015
+  name: Golden Signals
+  category: Core
+  description: Latency/Traffic/Errors/Saturation
+  example: Focus dashboards on these 4 metrics
+  level: beginner
+- id: OBS-016
+  name: RED Method
+  category: Core
+  description: Rate/Errors/Duration for services
+  example: Request-centric monitoring
+  level: intermediate
+- id: OBS-017
+  name: USE Method
+  category: Core
+  description: Utilization/Saturation/Errors for resources
+  example: Resource-centric monitoring
+  level: intermediate
+- id: OBS-018
+  name: Observability vs Monitoring
+  category: Core
+  description: Understanding internal state vs watching metrics
+  example: Monitoring = known unknowns, Observability = unknown unknowns
+  level: beginner
+- id: OBS-019
+  name: High Cardinality
+  category: Core
+  description: Too many unique label values
+  example: user_id as label = cardinality explosion
+  level: advanced
+- id: OBS-020
+  name: Cost Optimization
+  category: Core
+  description: Managing observability costs
+  example: Sample, aggregate, tier storage
+  level: advanced
+- id: OBS-021
+  name: Shift-Left Observability
+  category: Core
+  description: Add observability early in dev
+  example: Include in CI/CD pipelines
+  level: intermediate
+- id: OBS-022
+  name: Observability as Code
+  category: Core
+  description: Define dashboards/alerts in code
+  example: Terraform/Pulumi for Grafana
+  level: advanced
+- id: OBS-023
+  name: Service Maps
+  category: Core
+  description: Visualize service dependencies
+  example: Auto-generated from traces
+  level: intermediate
+- id: OBS-024
+  name: Anomaly Detection
+  category: Core
+  description: Automatically find abnormal patterns
+  example: ML-based alerting
+  level: advanced
+- id: OBS-025
+  name: Root Cause Analysis
+  category: Core
+  description: Determine why issues occurred
+  example: Correlate traces, logs, metrics
+  level: intermediate
+- id: OBS-026
+  name: MTTR Reduction
+  category: Core
+  description: Mean Time To Recovery
+  example: Better observability = faster debugging
+  level: intermediate
+- id: OBS-027
+  name: Unified Platform
+  category: Core
+  description: Single pane of glass for all signals
+  example: Grafana, Datadog, New Relic
+  level: intermediate
+- id: OBS-028
+  name: AIOps Integration
+  category: Core
+  description: AI-powered operations
+  example: Predictive alerts, auto-remediation
+  level: advanced
+- id: OBS-029
+  name: Edge Observability
+  category: Core
+  description: Monitor at edge/CDN level
+  example: Real user metrics from edge
+  level: advanced
+- id: OBS-030
+  name: Continuous Profiling
+  category: Core
+  description: Always-on performance profiling
+  example: 4th pillar of observability
+  level: advanced