skills.rest
syntropic137
syntropic137OFFICIAL
Explore all skills by this author →
GitHub

observability-queries

Provides validated LogsQL, PromQL, and Jaeger trace queries for telemetry retrieval.

Updated May 28, 2026
Search Tags:#debugging#logs#metrics#observability#traces#promql#trace-correlation
One-click install
npx skills add https://github.com/syntropic137/harness-app-template --skill observability-queries
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: observability-queries
Source: https://github.com/syntropic137/harness-app-template/tree/main/.claude/skills/observability-queries
Command: npx skills add https://github.com/syntropic137/harness-app-template --skill observability-queries

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually sifting through scattered logs, metrics, and traces to debug application issues or build evidence bundles is time-consuming and error-prone, especially when working with polyglot stacks and multiple observability tools.

Core Features & Use Cases

  • Pre-built query templates: Ready-to-use LogsQL, PromQL, and Jaeger-compatible trace queries for common debugging tasks like error scanning, latency checks, and trace-to-log correlation.
  • Built-in best practices: Includes critical gotchas (e.g., severity vs level field naming, mandatory field projections, case-sensitivity rules) to avoid silent query failures and performance issues.
  • Use case: When a Playwright end-to-end test fails, use this skill to quickly pull related error logs, error rate metrics, and trace data to identify the root cause without writing custom queries from scratch.

Quick Start

Use the observability-queries skill to pull all logs, metrics, and trace data for a failed Playwright test run to identify the root cause of the failure.

Frequently Asked Questions about observability-queries

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

FAQPage Schema
How do I query logs and traces to debug a failed Playwright test?▼

You can retrieve logs, metrics, and trace data for a failed Playwright test by using pre-validated query templates to pull error logs, error rate metrics, and trace data without writing custom queries.

What is the best way to correlate logs, metrics, and traces for a polyglot application?▼

Correlating logs, metrics, and traces for a polyglot application requires end-to-end workflows using pre-built LogsQL, PromQL, and Jaeger-compatible templates that apply correct syntax and mandatory field projections.

Can I use these observability queries with the Victoria metrics stack?▼

Yes, these query templates are specifically designed for retrieving logs, metrics, and traces from Victoria observability stack components to support bug investigation and alert configuration.

Why do my PromQL log queries fail silently when scanning for errors?▼

Log and PromQL queries fail silently due to platform-specific gotchas like incorrect severity versus level field naming, missing mandatory field projections, and case-sensitivity rule violations.

How do I create an evidence bundle from observability data for bug investigation?▼

You can create an evidence bundle during bug investigation by applying pre-built query templates to extract correlated logs, metrics, and traces, ensuring correct syntax and performant telemetry retrieval.

Related Skills

Explore More Software Engineering Skills→
wildbitcawildbitca
1

common-observability

Standardize logs, traces, and metrics across polyglot microservices with OpenTelemetry.

Official
Advanced
jayhjenkinsjayhjenkins
1

root-cause-diagnosis

Diagnose metric anomaly root causes using 4-dimension segmentation and hypothesis testing.

Community
Basic
petrkindlmannpetrkindlmann
64

observability-driven-testing

Convert production traces, logs, and telemetry into actionable tests.

Community
Advanced
pantheon-orgpantheon-org
9

promql-validator

Validate PromQL queries for syntax errors and anti-patterns.

Official
Intermediate