Skill UI

Expert skill in designing and implementing comprehensive observability stacks for enterprise microservices. Covers advanced monitoring (Prometheus, Grafana), distributed tracing (Jaeger, OpenTelemetry), centralized logging (ELK, Splunk), and defining SLIs/SLOs. Ideal for ensuring high availability, mastering incident response, and performing reliability engineering on large-scale, distributed applications.

This skill specializes in implementing Service Level Objectives (SLOs) and Service Level Indicators (SLIs) to enforce reliability standards. It guides users in designing comprehensive SLO frameworks, calculating error budgets, and building robust monitoring systems. Use this when you need to establish data-driven reliability targets, balance feature velocity with technical health, and align service performance directly with core business objectives.

Provides a thorough guide to observability patterns for Istio, Linkerd, and service mesh deployments, covering metrics, tracing, logging, dashboards, and troubleshooting workflows so engineers can set up monitoring, define SLOs, and investigate latency or error issues.

Defines and enforces SLIs, SLOs, and error budgets with Prometheus rules and alerts so teams can balance reliability targets with development velocity across availability, latency, and durability metrics.

Provides SRE guidance for defining SLIs/SLOs, managing error budgets, automating toil, and configuring monitoring/alerting so teams can scale reliable services and respond to incidents effectively.

Defines and monitors SLAs, SLIs, and SLOs so teams can set performance targets, track metrics like error budgets and availability, and react before issues impact customers.

This skill integrates LangChain 1.0 and LangGraph 1.0 into standard OpenTelemetry (OTEL) backends (e.g., Jaeger, Honeycomb, Tempo). It solves critical observability gaps by ensuring correct prompt content capture, propagating spans across complex subgraphs, and providing five LLM-specific Service Level Objectives (SLOs) like latency and cost. Ideal for multi-tenant, compliance-sensitive, or existing OTEL stack environments where LangSmith is unsuitable.