Skill UI

This skill automatically generates an interactive SQL Notebook designed to validate changes in dbt models or snapshots. It processes changes identified from a GitHub PR or local repository, generating comparison queries that compare 'before' (production) and 'after' (development) data states. It is essential for embedding data observability and quality checks into CI/CD pipelines.

OpenSearch is a distributed search and analytics engine integrated into the KubeSphere WizTelemetry Observability Platform. It is crucial for storing, searching, and analyzing various types of observability data, including application logs, system events, audit records, and notification history. This guide covers installation, configuration, and operational best practices for managing the OpenSearch cluster within KubeSphere.

This service provides a centralized, common API server backend for the entire KubeSphere WizTelemetry Observability Platform. It unifies backend functionalities for core observability components including Logging, Auditing, Events, Tracing, and Notifications, enabling global monitoring and streamlined platform management within Kubernetes environments. Use it when installing or configuring the core telemetry platform.

WizTelemetry Logging is a core extension component within the KubeSphere Observability Platform, designed for comprehensive log collection, processing, and storage. It supports advanced log collection architectures, including collecting container stdout/stderr logs (via vector-logging) and collecting logs directly from the container filesystem (via logsidecar-injector). Use this guide to understand its configuration, dependencies, and how to query logs using the dedicated API.

This guide provides comprehensive instructions for setting up monitoring and observability for Qdrant deployments. It helps users track critical performance metrics, check system health, and diagnose complex production issues such as memory growth or slow query requests. Use cases include setting up Prometheus, Grafana, and implementing robust health checks.

A comprehensive guide to implementing observability for Klaviyo API integrations. This solution uses Prometheus metrics (counters, histograms, gauges) to track API volume, latency, and errors, combined with OpenTelemetry for distributed tracing and structured logging. Ideal for setting up robust monitoring dashboards and critical alerting systems for marketing data pipelines.

A logging wrapper designed to instrument and monitor calls to the Claude API. It automatically tracks critical metrics including token usage, API latency, estimated cost, and error details. Essential for implementing robust observability patterns and setting up proactive alerts in production environments.

This guide details how to implement comprehensive observability for various Adobe API integrations (e.g., Firefly, PDF Services). It covers the four pillars of observability: structured metrics using Prometheus, distributed tracing via OpenTelemetry, structured JSON logging, and defining critical alert rules. This ensures deep visibility into API performance, latency, and error rates for robust production monitoring.

This skill provides a comprehensive guide to instrumenting Algolia search services for enterprise-grade observability. It integrates core monitoring patterns, including Prometheus metrics (latency, error rates, request counts), OpenTelemetry distributed tracing, and structured logging. Use this to achieve deep insights into search performance, user experience, and system health in production environments.

This module provides comprehensive observability for Anthropic's Claude API integrations. It enables the tracking of critical operational metrics including latency, token usage (input/output), estimated API costs, and error rates. Use it to set up structured logging and Prometheus metrics for robust monitoring and alerting, ensuring reliable and cost-effective AI application deployments.

A comprehensive checklist for deploying Claude API integrations to a production environment. It covers essential best practices for reliability, observability, and cost control, including authentication procedures, advanced error handling, rate limit management, health check implementation, and infrastructure deployment strategies (e.g., canary releases) to ensure a smooth and stable launch.

This guide provides a comprehensive observability stack for Apple Notes on macOS. Since Notes lacks a built-in metrics API, this solution demonstrates how to monitor key health indicators—such as note/folder counts, system latency, and iCloud sync daemon status—by polling via JXA and Bash scripts. It includes scripts for scheduled health checks, trend visualization, and robust error handling for production monitoring environments.