81 skills · sorted by relevance
Configure GKE logging, metrics collection, dashboards, and alerts with Cloud Logging, Cloud Monitoring, and managed Prometheus. Diagnose missing measurements, collection failures, permission errors, and alert rule problems to identify appropriate configuration changes.
Export recorded AI usage costs and budgets as Prometheus metrics or JSON. Feed external dashboards with totals, model tier breakdowns, session costs, and budget utilization, or send the same data to a webhook endpoint.
Configure Prometheus to collect and store operational metrics from infrastructure and applications. Covers collection schedules, alert rules, automatic discovery of monitored services, and troubleshooting checks to help establish and maintain monitoring.
Query Prometheus metrics through Grafana and manage dashboards as JSON files. Use it to investigate current values and trends, add or adjust panels, and preview dashboard updates before applying them.
Design service monitoring with Prometheus, write PromQL queries to analyze metrics, and build Grafana dashboards. Configure actionable alerts and manage metric labels so monitoring stays useful as the volume of collected data grows.
Define service reliability measurements and targets, then turn them into Prometheus monitoring rules and alerts. Calculate error budgets, the amount of failure allowed, and outline Grafana dashboards for tracking reliability and deciding when to prioritize fixes.
Set up application monitoring with structured logs, performance metrics, and traces that follow requests across services. Build dashboards and alerts, run load tests, investigate CPU and memory bottlenecks, and estimate future infrastructure capacity.
Add structured logs, performance metrics, and traces that follow requests across Python services. Establish consistent log fields and request IDs so production failures can be investigated using recorded activity and service health signals.
Prometheus provider for obz. Covers all 6 metric commands using standard PromQL. This skill should be used when the user mentions "Prometheus", "PromQL", "obz metric -p prom", or needs to query metrics from a Prometheus server.
The English summary is being prepared. Showing the original description.
Design production alerts, route notifications by severity, and organize on-call schedules. Use configuration examples to define backup contacts, escalation steps when alerts go unanswered, and runbooks that guide responders through incident investigation.
Build Grafana dashboards that show application and infrastructure health through request rates, errors, response times, and resource usage. Organize metrics into useful panels, add filters and alerts, and manage dashboard definitions as code.
Create and validate Terraform alerts for GKE using PromQL, a monitoring query language. Cover response times, errors, traffic, memory usage, and cluster health, with checks for alert timing, duplicate signals, and metric ingestion costs.
Define reliability targets for production services and calculate error budgets, the allowed amount of failure. Create monitoring rules, incident response runbooks, capacity plans, and automation scripts, with failure experiments to check recovery behavior.
Plan, implement, or review prometheus configuration work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests prometheus configuration work.
The English summary is being prepared. Showing the original description.
Site reliability specialist for Prometheus metrics, distributed tracing, alerting strategies, and SLO designUse when "observability, monitoring, prometheus, grafana, alerting, slo, sli, metrics, tracing, logging, on-call, incident, observability, prometheus, grafana, tracing, jaeger, alerting, slo, sli, metrics, logging, sre, ml-memory" mentioned.
The English summary is being prepared. Showing the original description.
Query and manage Grafana dashboards and Prometheus metrics for Happy infrastructure. Covers grafanactl CLI usage, direct Prometheus queries through Grafana proxy, and dashboard-as-code workflows. Use when user asks about metrics, dashboards, monitoring, Grafana, Prometheus, or wants to add/modify panels.
The English summary is being prepared. Showing the original description.
Reviews Prometheus instrumentation in Go code for proper metric types, labels, and patterns. Use when reviewing code with prometheus/client_golang metrics.
The English summary is being prepared. Showing the original description.
インフラストラクチャとアプリケーションの包括的なメトリクス収集、ストレージ、モニタリングのためのPrometheusをセットアップします。メトリクス収集の実装、モニタリングインフラストラクチャのセットアップ、アラートシステムの設定時に使用します。
The English summary is being prepared. Showing the original description.
Develop incident response procedures for LLM outages, declining answer quality, spending spikes, and unsafe outputs. Use example monitoring alerts, severity levels, recovery playbooks, and postmortem guidance to organize detection, response, and follow-up work.
Add monitoring to AI agents with response times, token usage, estimated costs, and error metrics. Trace records follow model and tool calls step by step, helping teams investigate failures and understand operating costs.
Deploy language models with vLLM through an OpenAI-compatible API or offline batch processing. Tune response speed, throughput, and GPU memory use with quantization, which reduces numerical precision, and execution across multiple GPUs.
Turn existing PromQL or ListTimeSeries queries into Cloud Monitoring chart definitions in textproto, a text format for Protocol Buffers. Generate readable titles, axis labels, units, and plot types, then validate the resulting widget files.
Install and configure WizTelemetry Platform Service, the shared API backend for KubeSphere observability extensions. Generate configuration based on installed extensions, update installation settings, and inspect service health, pods, and logs.
Use this skill to deploy and operate a CollectX (clx) based DOCA telemetry collector on a host or BlueField — wiring providers / counters into the collector, running the collection daemon, and shaping its exporters (Prometheus pull, Fluent Bit push, NetFlow, file / IPC) so the metrics actually leave the box. Trigger even when the user never says CollectX or clx — implicit phrasings: {collector emits nothing downstream}, {add a provider to the clx collector}, {turn on the Prometheus endpoint}, {ship counters to Fluent Bit from the DPU}, {daemon starts but no schema rows appear}. This skill owns the CollectX collection mechanism plus the operator's own doca-telemetry / doca-telemetry-exporter usage; it ROUTES the productized DOCA Telemetry Service (DTS) to public docs (AGENTS.md Non-goal #7), the reader API to doca-telemetry, and the publisher API to doca-telemetry-exporter. Refuse to invent clx symbols, provider names, schema fields, flags, or config paths — describe the class and route to the live source.
The English summary is being prepared. Showing the original description.