perses-datasource-manage

Manage Perses datasources across global, project, and dashboard scopes.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill perses-datasource-manage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: perses-datasource-manage
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/perses-datasource-manage
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill perses-datasource-manage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Perses datasource lifecycle management across global, project, and dashboard scopes enables teams to create, update, and delete datasources consistently.

Core Features & Use Cases

  • Lifecycle management across global, project, and dashboard scopes for multiple backend types.
  • MCP-first workflow with perCLI fallback to manage Prometheus, Tempo, Loki, Pyroscope, ClickHouse, and VictoriaLogs datasources.
  • Always apply scope precedence rules (Dashboard > Project > Global) and configure HTTP proxy endpoints as needed.
  • Use cases include centralized defaults, per-team overrides, and dashboard-specific configurations.

Quick Start

Configure a global Prometheus datasource using MCP with percli fallback.

Frequently Asked Questions about perses-datasource-manage

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

FAQPage Schema
How do I manage Perses datasources across different scopes?

Manage Perses datasources across global, project, and dashboard scopes by creating, updating, and deleting configurations. The workflow enforces scope precedence rules where Dashboard overrides Project, which overrides Global settings.

Can I configure Prometheus and Loki datasources in Perses using MCP?

Yes, you can configure Prometheus, Tempo, Loki, Pyroscope, ClickHouse, and VictoriaLogs datasources using an MCP-first workflow. It includes a percli fallback to ensure safe and auditable changes when MCP is unavailable.

What is scope precedence when creating a Perses datasource?

Scope precedence in Perses datasources dictates that Dashboard scope overrides Project scope, which in turn overrides Global scope. This hierarchy enables centralized defaults with specific per-team or dashboard-level overrides.

How do I set up a global Prometheus datasource in Perses?

Configure a global Prometheus datasource using the MCP workflow with percli fallback. Validate HTTP proxy endpoint configurations and default behaviors to ensure safe, auditable changes across your Perses environment.

Does this workflow validate HTTP proxy endpoints for Perses datasources?

Yes, the workflow validates HTTP proxy endpoint configurations alongside scope precedence and default behaviors. This validation ensures safe and auditable datasource lifecycle changes across global, project, and dashboard scopes.

What is the best way to override a global datasource for a specific dashboard?

Apply dashboard scope precedence to override global or project datasource configurations. This approach allows dashboard-specific configurations while maintaining centralized defaults for Prometheus, Loki, or other supported backends.