metrics

Automate Prometheus metric queries with PromQL templates for HTTP and GenAI monitoring.

34|32|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/opensearch-project/observability-stack --skill metrics-opensearch-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metrics
Source: https://github.com/opensearch-project/observability-stack/tree/main/claude-code-observability-plugin/skills/metrics
Command: npx skills add https://github.com/opensearch-project/observability-stack --skill metrics-opensearch-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prometheus metrics are powerful but require crafting PromQL queries to extract meaningful signals; this skill provides ready-to-use templates for HTTP rates, latency percentiles, error rates, active connections, and GenAI token usage to speed up monitoring and troubleshooting.

Core Features & Use Cases

  • Ready-made PromQL templates for common HTTP and GenAI metrics
  • Flexible querying across services, time windows, and metric name variants
  • Use case: rapidly diagnose SLA breaches by correlating request rates, latencies, and error rates across services

Quick Start

Query Prometheus using the provided PromQL templates against http://localhost:9090/api/v1/query to fetch HTTP rates, latency, errors, and GenAI token usage.

Frequently Asked Questions about metrics

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

FAQPage Schema
How do I query Prometheus for HTTP request latency and error rates?

Query Prometheus for HTTP request latency and error rates using ready-made PromQL templates that target the default endpoint at http://localhost:9090/api/v1/query to fetch and correlate performance metrics across microservices.

Can I monitor GenAI token usage with PromQL in a microservice environment?

Yes, you can monitor GenAI token usage with PromQL using provided templates designed to track token consumption rates and analyze usage patterns across services and time windows within your microservice environment.

What's the best way to diagnose SLA breaches using Prometheus metrics?

Diagnose SLA breaches using Prometheus metrics by correlating request rates, latency percentiles, and error rates across services with pre-built PromQL templates to rapidly identify performance bottlenecks.

Do I need a running Prometheus endpoint to query microservice metrics?

Yes, you need a reachable Prometheus endpoint, defaulting to http://localhost:9090, to execute the curl-based query patterns and retrieve HTTP rates, active connections, and GenAI token usage data.

How do I handle different metric name variants when querying Prometheus?

Handle different metric name variants when querying Prometheus by applying the skill's flexible template configurations, which support selecting and filtering multiple metric name variants by service and time range.