Connect Prometheus®.

Connect your Prometheus metrics to Perfloop. Use labels to choose the services and environments it can read.

Access you need

• read-only authorization Create a credential that can use the Prometheus HTTP query API. Enter the complete Authorization header value, such as Bearer …or Basic …. Do not use a credential with write or administration access.

• label selectors Register one or more label selectors with exact values, such as {service="api",env="prod"}. Every query must keep that selector.

• HTTPS endpoint Use your Prometheus base URL, such as https://prometheus.example.com. Put credentials in the Authorization field, not the URL.

Setup

1 · create a read credential

Use your gateway or identity provider to create a credential that can read the Prometheus query API.

2 · set the endpoint and scopes

In Perfloop Setup, select Prometheus. Enter the endpoint, complete Authorization value, and one exact label selector for each service or environment.

3 · connect to Perfloop

Perfloop checks the endpoint, credential, and every selector before it saves the new connection.

An Admin's coding agent can return a Setup link that opens this provider's form. Complete the form in Setup, and never paste a credential into chat or an MCP call.

Data Perfloop reads

• Discovery metadata. Metric names and labels for the services and environments you selected.

• Metric results. Instant and range responses can contain metric labels, sample values, and provider warnings.

• Stored results. The query, without credentials, and its response can be retained.

For Elasticsearch 9.5 time-series data streams (TSDS) named metrics-*, select Prometheus and use an HTTPS endpoint ending in /_prometheus. Use an API key with read and view_index_metadata on the selected streams. If you use the relay, put this endpoint and the Authorization: ApiKey … header in its upstream configuration; enter the relay name in Perfloop. This reads TSDS metrics, not classic APM transactions or Universal Profiling data.

Repo access

Work on any repo in the workspace can query the selected scopes of every telemetry connection in the workspace. Keep telemetry that some repos must not read in a separate workspace.

Credentials and network access

Perfloop encrypts the credential and uses it only for requests within your connection's scope. Models and execution sandboxes do not receive it.

Use a public HTTPS endpoint with a valid certificate. For a Prometheus® the internet cannot reach, run the Perfloop relay in your network and enter relay://name as the endpoint. The provider credential then lives in the relay configuration; leave the Authorization field in Setup empty.

Change or remove access

In Setup, select Edit on the source's row under Configured sources, change the credential, endpoint, or selector list, then select Save connection. The saved connection changes only after every new value validates. Revoke the credential in your provider to stop later reads.

To remove a source, select Delete on its row and confirm. Perfloop deletes the credential it stores, and scheduled checks on the source stop running. Their saved queries and past results stay.

Provider documentation

• Prometheus basic authentication

• Prometheus HTTPS and authentication

Security questions: security@perfloop.ai