Skill Detail

Use GreptimeDB for agent observability telemetry and root cause analysis

Store OpenTelemetry metrics, logs, traces, and GenAI telemetry in one queryable backend so agents can correlate incidents and root-cause signals with SQL or PromQL.

Monitoring & AlertsMulti-Framework
Monitoring & Alerts Multi-Framework Security Reviewed
⭐ 6.7k GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill use-greptimedb-for-agent-observability-telemetry-and-root-cause-analysis Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
GreptimeDB, OpenTelemetry Collector or compatible telemetry pipeline, SQL or PromQL query access, optional Grafana or Greptime dashboard
Install & setup
Follow the GreptimeDB installation guide for Docker, binary, or Kubernetes deployment, configure OpenTelemetry or Prometheus/Loki/Elasticsearch-compatible ingestion, then give the agent the documented GreptimeDB skill instructions at https://docs.greptime.com/SKILL.md before it queries telemetry.
Author
GreptimeTeam
Publisher
Organization
Last updated
Sep 20, 2026
Quick brief

Use GreptimeDB when an operator wants an agent to work from a durable observability database instead of ad hoc log snippets or a single dashboard. The agent can help configure OpenTelemetry, Prometheus Remote Write, Loki Push, or Elasticsearch Bulk ingestion, query metrics/logs/traces with SQL or PromQL, and correlate shared identifiers such as service, host, and trace ID during incident analysis. Invoke this when the user needs a self-hosted telemetry backend for agent RCA or GenAI observability, not when they only need to click around the Greptime product UI. The scope boundary is ingesting and querying observability data for supervised diagnostics; it is not a general database framework listing or a replacement for application instrumentation.

How it works

What this skill actually does

Inputs and prerequisites: GreptimeDB, OpenTelemetry Collector or compatible telemetry pipeline, SQL or PromQL query access, optional Grafana or Greptime dashboard.

Setup notes: Follow the GreptimeDB installation guide for Docker, binary, or Kubernetes deployment, configure OpenTelemetry or Prometheus/Loki/Elasticsearch-compatible ingestion, then give the agent the documented GreptimeDB skill instructions at https://docs.greptime.com/SKILL.md before it queries telemetry.

Source and verification boundary: use https://docs.greptime.com/SKILL.md as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.