kubeblocks-setup-monitoring

Route monitoring requests to existing or bootstrap observability stacks for KubeBlocks clusters.

3|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-setup-monitoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubeblocks-setup-monitoring
Source: https://github.com/apecloud/kubeblocks-skills/tree/main/skills/kubeblocks-setup-monitoring
Command: npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-setup-monitoring

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Route monitoring requests to the appropriate operational path (existing stack or bootstrap) for KubeBlocks clusters.

Core Features & Use Cases

  • Decides between reusing an existing Prometheus/Grafana setup and bootstrapping a new observability stack.
  • Provides explicit readiness signals such as metrics-ready, scrape-ready, dashboard-ready, and alerting-ready.

Quick Start

Issue a monitoring request with a clear goal, and the skill will route it to the correct leaf skill based on the environment context.

Frequently Asked Questions about kubeblocks-setup-monitoring

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

FAQPage Schema
How do I set up monitoring for KubeBlocks clusters?

KubeBlocks monitoring can be set up by routing requests to either bootstrap a new observability stack or reuse an existing Prometheus and Grafana setup based on your environment context.

Can I use my existing Prometheus and Grafana stack with KubeBlocks?

Yes, you can reuse an existing Prometheus and Grafana stack. The routing mechanism detects your current environment and directs monitoring requests to the appropriate operational path.

What readiness signals are provided when bootstrapping a KubeBlocks observability stack?

Bootstrapping a KubeBlocks observability stack provides explicit readiness signals including metrics-ready, scrape-ready, dashboard-ready, and alerting-ready statuses to track deployment progress.

How does smart routing work for KubeBlocks observability?

Smart routing for KubeBlocks observability evaluates environment context to automatically direct monitoring requests to the correct leaf skill, deciding between reusing existing stacks or bootstrapping.

When should I bootstrap a new observability stack instead of reusing one?

You should bootstrap a new observability stack when no existing Prometheus or Grafana stack is detected, allowing KubeBlocks to deploy a fresh monitoring environment with explicit readiness signals.