Prometheus Plugin
The Prometheus plugin is a metric source plugin that lets Konduo query Prometheus-compatible HTTP APIs and execute resource-owned logical metrics as PromQL queries.
Highlights
- Executes range and instant queries for resource dashboards and alert evaluation.
- Supports label exploration, query inspection, and mapping-pack review.
- Can register a Prometheus server itself as a resource to inspect targets, TSDB, rule/evaluation, and runtime signals.
- Protects management actions such as reload and snapshot behind configuration, confirmation, and cooldown controls.
Before Registration
- The Konduo backend must be able to reach the Prometheus HTTP API.
- Prepare endpoint URL, authentication mode, timeout, and query-limit policy.
- Apply resource plugin mapping packs so dashboards and alert rules can resolve expected logical metrics.
Operations Tips
- If dashboards are empty, check scrape state, label filters, and mapping-pack installation together.
- Bound query ranges and steps to avoid excessive sample volume.
- Treat Prometheus target health as metric evidence, not as the direct availability source for the scraped resource.
Prometheus Enterprise Overlay
The Prometheus Enterprise overlay adds MCP descriptors and Prometheus self-telemetry anomaly rules to metric source resources. It detects metric platform risk through scrape, ingestion, cardinality, and query pressure signals.
Highlights
- Exposes Prometheus resource metadata, diagnostics, metrics catalog, and anomaly rules through MCP.
- Declarative metric rules use logical metrics such as scrape duration, ingestion rate, TSDB head series, and query rate.
- Simulator series validate cardinality and ingestion pressure scenarios.
- Prometheus remains a metric provider and does not run plugin-mode detectors.
Before Registration
- Prometheus API endpoint and query permissions must be healthy.
- Connect a mapping pack for Prometheus self-metrics.
- MCP users need metric-source read permission and the required scopes.
Operations Tips
- Track cardinality growth together with exporter, label, and instrumentation changes.
- When scrape latency and ingestion pressure rise together, inspect target growth and remote write state.