Prometheus

The Prometheus tool lets a workbench agent query metrics from a Prometheus-compatible endpoint. Configure the connection once, then attach it to the workbenches that should use it.

Prerequisites

Before you begin, make sure you have:

• A Prometheus-compatible query endpoint (Prometheus, Mimir, Cortex, Thanos, or Amazon Managed Prometheus) that is already receiving the metrics you want the workbench to query.
• Permission in Plural Console to create a configured tool and edit the target workbench.
• Credentials for the endpoint: basic auth username/password, a bearer token, AWS SigV4 access (for Amazon Managed Prometheus), or no authentication if the endpoint is already network-restricted.
• An existing workbench, or permission to create one.

Prepare read-only access

Create a dedicated identity for this integration and grant it query-only access in your gateway or proxy layer — avoid exposing write or admin endpoints to it.

Capabilities

• workbench_observability_metrics — Run a PromQL range query against the endpoint over a time range, with an optional step resolution (defaults to 30 seconds if omitted). Queries must cover less than 7 days.
• workbench_observability_metric_search — Search metric names (the __name__ label) seen on the endpoint in the last 24 hours, optionally filtered by a substring.
• workbench_observability_metric_label_search — For a given metric, search its label names, or its values for a specific label, also over the last 24 hours.

This tool is read-only and registers only these metrics operations — Prometheus has no logs, traces, dashboard, or monitor capability in Workbenches.

Create the Prometheus tool