Learn how to connect monitoring data for your Kubernetes workloads.
S‌edai ingests monitoring data to understand cloud infrastructure, learn resource behavior, and inform its decision engine.
You can connect Prometheus when you connect a Kubernetes cluster to Sedai for the first time, or add it to an existing cluster within Sedai at any time from the Settings > Integrations page.
If Prometheus is your primary monitoring source, you will need to connect it to each Kubernetes cluster that is added to Sedai.
Sedai can receive monitoring data from multiple Prometheus instances running in an on-premise or public cloud.
To connect to Prometheus, you will need to provide its Endpoint. By default, Sedai does not require authentication since it assumes it can connect to Prometheus within the Kubernetes control plane via the Sedai Smart Agent.
If you need to authenticate Prometheus, select your preferred connection method below to view its requirements:
Select a connection method to view its requirements:
Basic Auth
  • Username
  • Password
JWT Credentials
  • Token
OIDC Client Credentials
  • Token Endpoint
  • Client ID
  • Client Secret
OIDC Resource Owner Password
  • Token
  • Client ID
  • Client Secret
  • Username
  • Password

Advanced Setup

Certificate Authority

If you use custom CA (Certification Authority) for https connection while communicating with Prometheus endpoint, you can optionally provide it in PEM format.


Sedai leverages tags to accurately infer metrics and map them to your infrastructure. This allows it to correlate metrics to corresponding resources it discovers within the connected account/cluster.
By default, Sedai pre-populates standard tag values based on industry best practices for naming conventions. However, if you configured custom tags, you will need to provide the exact tag value used for the following topology elements:
Default Label Value
exporter_namespace, envoy, namespace, destination_service_namespace
Load Balancer