ops-telemetry-query

Query Boundless telemetry views for broker heartbeats, evaluations, and completions.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Current-cmd/PlsTrustMe --skill ops-telemetry-query-current-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ops-telemetry-query
Source: https://github.com/Current-cmd/PlsTrustMe/tree/main/.claude/skills/ops-telemetry-query
Command: npx skills add https://github.com/Current-cmd/PlsTrustMe --skill ops-telemetry-query-current-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables Boundless operators and engineers to retrieve broker telemetry data from the Redshift-compatible warehouse to diagnose health, latency, and reliability issues across prod and staging environments.

Core Features & Use Cases

  • Connect to the telemetry data warehouse using a Redshift URL, read credentials from repository secrets or direct input, and translate addresses with network_address_labels.json for readable output.
  • Query the three telemetry views (telemetry.broker_heartbeats, telemetry.request_evaluations, telemetry.request_completions) to analyze broker health, decision evaluations, and completion metrics in real time.
  • Provide environment-aware context and label mappings to improve runbook readability and incident response.

Quick Start

Export REDSHIFT_URL or provide credentials, then run a sample query against the telemetry views to retrieve recent broker data.

Frequently Asked Questions about ops-telemetry-query

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

FAQPage Schema
How do I query broker heartbeat telemetry data from a Redshift warehouse?

To query broker heartbeat telemetry, connect to your Redshift-compatible warehouse using a configured REDSHIFT_URL and query the telemetry.broker_heartbeats view to retrieve latest health status across environments.

What telemetry views are available for monitoring Boundless broker health and request metrics?

Boundless telemetry monitoring uses three Redshift schema views: telemetry.broker_heartbeats for health status, telemetry.request_evaluations for decision metrics, and telemetry.request_completions for operational timing data.

Do I need to configure separate credentials to query telemetry data across prod and staging environments?

Yes, querying telemetry data across prod and staging requires environment-aware credentials. You must supply a Redshift URL with sslmode and configure repository secrets to ensure environment-specific access.

How do I map raw network addresses to readable labels when analyzing broker telemetry?

You can map raw network addresses to readable labels by supplying a canonical address label mapping using network_address_labels.json, which translates addresses for improved runbook readability during telemetry analysis.

What is the best way to diagnose broker latency and reliability issues using telemetry data?

The best way to diagnose broker latency and reliability issues is querying telemetry.request_evaluations and telemetry.request_completions views in Redshift to analyze decision metrics and operational timing across environments.