metrics-server

Ingest OTLP telemetry into DuckDB and export benchmark reports via HTTP API.

3.1k|376|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Mesh-LLM/mesh-llm --skill metrics-server
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metrics-server
Source: https://github.com/Mesh-LLM/mesh-llm/tree/main/.agents/skills/metrics-server
Command: npx skills add https://github.com/Mesh-LLM/mesh-llm --skill metrics-server

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Benchmark telemetry data is often fragmented across experiments and runs. metrics-server centralizes ingestion, lifecycle management, and report export for reliable benchmarking.

Core Features & Use Cases

  • Ingests and stores OTLP telemetry data into a DuckDB-backed store.
  • Manages run lifecycle and coordinates benchmark stages with OTLP data.
  • Exports standardized benchmark reports via HTTP API (e.g., report.json).

Quick Start

Start metrics-server to collect telemetry and generate benchmark reports.

Frequently Asked Questions about metrics-server

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

FAQPage Schema
How do I collect and store OTLP telemetry data for benchmark suites?

To store OTLP telemetry data for benchmark suites, metrics-server ingests streams directly into a DuckDB-backed store, centralizing run lifecycle management and coordinating benchmark stages for reliable data collection.

What is the best way to export standardized benchmark reports from telemetry runs?

To export standardized benchmark reports, metrics-server orchestrates report generation via an HTTP API, outputting files like report.json from stored telemetry data.

Can I use DuckDB to manage benchmark telemetry lifecycle and stage-run workflows?

Yes, you can use DuckDB to manage benchmark telemetry lifecycle and stage-run workflows. metrics-server applies DuckDB storage to centralize ingestion and coordinate OTLP data across benchmark stages.

Does metrics-server support receiving telemetry data from OTLP endpoints?

Yes, metrics-server supports receiving telemetry data from OTLP endpoints. It ingests OTLP streams, stores them in DuckDB, and coordinates benchmark stages with the collected telemetry data.

Why should I centralize benchmark telemetry data instead of leaving it fragmented across runs?

Centralizing benchmark telemetry data prevents fragmentation across experiments and runs. metrics-server provides a DuckDB-backed store and lifecycle management to ensure reliable benchmarking and standardized report exports.