skills.rest
metric-space-ai
metric-space-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

ticket-monitoring-ingest

Ingests monitoring snapshots from systems like Prometheus and Grafana into ticket context via CLI.

2|Updated Apr 12, 2026
Search Tags:#monitoring#observability#ingestion#grafana#tickets#prometheus#knowledge-plane
One-click install
npx skills add https://github.com/metric-space-ai/ctox --skill ticket-monitoring-ingest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ticket-monitoring-ingest
Source: https://github.com/metric-space-ai/ctox/tree/main/skills/system/ticket_integration/ticket-monitoring-ingest
Command: npx skills add https://github.com/metric-space-ai/ctox --skill ticket-monitoring-ingest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitoring data from systems like Prometheus, Grafana, uptime checks, and service dashboards often lives outside the ticket narrative. This skill ingests that evidence into the ticket knowledge plane to keep tickets grounded in observable reality.

Core Features & Use Cases

  • Ingest monitoring snapshots into ticket context for better triage and planning.
  • Maintain provenance and auditability by storing monitoring data in the knowledge plane's dedicated domain.
  • Use cases include incident triage, post-incident reviews, and root-cause analysis where dashboards reflect service state.

Quick Start

Run ctox ticket monitoring-ingest --system <system> --snapshot-json '<json>' to attach monitoring evidence to the ticket context.

Frequently Asked Questions about ticket-monitoring-ingest

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

FAQPage Schema
How do I ingest Prometheus or Grafana monitoring data into ticket context?▼

You can ingest monitoring data by running the ctox ticket monitoring-ingest command with your specified system and snapshot JSON, which populates the ticket knowledge plane with observable evidence.

What is the best way to attach dashboard evidence to incident triage tickets?▼

Attaching dashboard evidence to tickets requires ingesting monitoring snapshots into a dedicated knowledge plane domain, ensuring incident triage and root-cause analysis remain grounded in observable reality.

Why does monitoring data from uptime checks need to be stored in a knowledge plane?▼

Storing monitoring data in a knowledge plane preserves provenance and auditability, ensuring that service state evidence from uptime checks is directly reflected in the ticket narrative.

Can I use service dashboard snapshots for post-incident reviews in this system?▼

Yes, you can ingest service dashboard snapshots as monitoring evidence to support post-incident reviews, capturing the observable reality of the service state during the event.

How do I preserve provenance when importing observability data into tickets?▼

Preserving provenance is achieved by ingesting observability data into the knowledge plane's dedicated monitoring domain, which maintains an auditable record of the system and snapshot context.

Related Skills

Explore More Data & Analytics Skills→
jg-chalk-iojg-chalk-io

moai-domain-monitoring

Collect metrics, logs, and traces from Kubernetes microservices using Prometheus, Grafana, Loki, OpenTelemetry, and Jaeger.

Community
Advanced
leonardoteodorooleonardoteodoroo

postmortem-writing

Generate blameless postmortems with root cause analysis, timelines, and action items.

Community
Advanced
VincentChong123VincentChong123

add-dashboard

Integrate a monitoring dashboard into NanoClaw for agent activity and token usage.

Community
Intermediate
metric-space-aimetric-space-ai
2

ticket-knowledge

Loads and validates SQLite-backed ticket knowledge planes before executing ticket operations across systems.

Official
Intermediate