grafana-observability-stack

Configures a Grafana observability stack routing telemetry from microservices to Prometheus, Jaeger, Loki, and Grafana.

1|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/PremModhaOfficial/motadata-ai-pipeline --skill grafana-observability-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: grafana-observability-stack
Source: https://github.com/PremModhaOfficial/motadata-ai-pipeline/tree/main/.claude/skills/grafana-observability-stack
Command: npx skills add https://github.com/PremModhaOfficial/motadata-ai-pipeline --skill grafana-observability-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Grafana-based observability stack patterns for collecting metrics, traces, and logs from multi-tenant microservices using OpenTelemetry, Prometheus, Jaeger, Loki, and Grafana dashboards.

Core Features & Use Cases

  • OTel Collector-based data routing for metrics, traces, and logs
  • Per-tenant dashboard provisioning and alerting
  • Docker Compose dev stack and Kubernetes Helm deployment templates
  • Grafana datasource provisioning and dashboard templating

Quick Start

Deploy and configure a Grafana-based observability stack for multi-tenant microservices using the OpenTelemetry Collector, Prometheus remote-write, Jaeger, Loki, and Grafana dashboards.

Frequently Asked Questions about grafana-observability-stack

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

FAQPage Schema
How do I set up a Grafana observability stack for multi-tenant microservices?

A Grafana observability stack for multi-tenant microservices uses an OpenTelemetry Collector to route metrics, traces, and logs to Prometheus, Jaeger, and Loki. It provisions per-tenant dashboards and alert rules via Helm values templates across Docker Compose and Kubernetes deployments.

What is the best way to collect metrics, traces, and logs using OpenTelemetry in Kubernetes?

The best way to collect telemetry using OpenTelemetry in Kubernetes is configuring OTel Collector pipelines to route metrics to Prometheus, traces to Jaeger, and logs to Loki. This pattern provisions Grafana datasources and enables Loki-Jaeger trace linkage for end-to-end visibility.

Can I use Docker Compose for a local Grafana, Loki, and Jaeger development stack?

Yes, you can use Docker Compose for a local Grafana, Loki, and Jaeger development stack. The configuration provides Docker Compose dev stack templates that provision Grafana datasources and dashboards alongside OpenTelemetry Collector pipelines for local testing before Kubernetes deployment.

How do I configure per-tenant dashboards and alerting in Grafana?

To configure per-tenant dashboards and alerting in Grafana, apply Helm/values-based deployment patterns that provision datasources and dashboard templates. This enables per-tenant dashboard provisioning and alert rules within the unified observability stack for multi-tenant microservices.

How do I link Loki logs to Jaeger traces in an OpenTelemetry observability stack?

To link Loki logs to Jaeger traces in an OpenTelemetry observability stack, configure the OTel Collector pipelines to inject trace IDs into log outputs. This enables Loki-Jaeger trace linkage directly within the provisioned Grafana dashboards for end-to-end telemetry correlation.

Do I need Helm to deploy Prometheus and Loki on Kubernetes for multi-tenant observability?

Yes, you need Helm to deploy Prometheus and Loki on Kubernetes for multi-tenant observability. The configuration enforces a Helm/values-based deployment pattern to provision data sources, dashboards, and alert rules across the multi-tenant microservices observability stack.