Skip to main content
Telara

Integrations / Prometheus

Prometheus logo

Prometheus

Prometheus monitoring system and time series database

Bearer token
Indexes
Actions

What Telara does

Capability matrix

Indexes YesTracks spend NoDiscovers shadow AI NoRuns actions YesReal-time events No

Before you connect

Prerequisites

A Prometheus (or compatible) HTTP API Telara can reach.
If the API is authenticated, a bearer token or basic user your admin issued for Telara.

Vendor setup

Get the credential

1
Copy the API base URL
From your Prometheus operator, copy the URL that serves /api/v1 (often the same host as the UI, sometimes a separate query frontend).
2
Create auth if required
If the API is public inside your network, Telara still needs a reachable URL. If it uses auth, create a dedicated token or username/password. Do not reuse a human SSO cookie.
3
Paste in Telara
Settings → Integrations → Prometheus. Enter the base URL and, if the form shows them, the bearer token or basic credentials.

In Telara

Connect in Telara

Bearer token

In Telara, open Settings → Integrations, choose this connector, and paste the bearer token into the field Telara shows.

Fields Telara asks for
  • Base Url
  • Bearer Token
Basic auth

In Telara, open Settings → Integrations, choose this connector, and enter the username and password (or key) Telara asks for.

Fields Telara asks for
  • Base Url
  • Username
  • Password

Knowledge

What gets indexed

ResourceCoverage
TargetPartial — not every record the vendor holds is synced
Alert rulePartial — not every record the vendor holds is synced

Sync

Freshness & sync

ResourceLagDeletions
TargetUp to 1 dayRemoved records disappear on the next full sync
Alert ruleUp to 1 dayRemoved records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Target, Alert rule.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Prometheus that is only on a cluster-internal service has no path for Telara unless you expose it.
Wrong base URL (UI without /api) authenticates nowhere.