# Grafana (/docs/foundation/components/grafana)



## Component Category [#component-category]

Monitoring and debugging / visualization

## Component Description [#component-description]

Grafana is the visualization and dashboarding layer for metrics, logs, and traces. BullSequana AI provisions platform dashboards from labeled Kubernetes `ConfigMap` resources and configures Prometheus, Loki, and Tempo as the core data sources.

## Why It Is Used [#why-it-is-used]

In BullSequana AI Foundation, Grafana gives operators a common interface for platform health, service metrics, logs, and distributed traces. Component-specific dashboards complement the cluster-wide Kubernetes views.

## Learn More [#learn-more]

* [Grafana documentation](https://grafana.com/docs/grafana/latest/)
* [grafana/grafana on GitHub](https://github.com/grafana/grafana)

## Dashboard provisioning [#dashboard-provisioning]

Grafana discovers dashboards from `ConfigMap` resources labeled with `grafana_dashboard=1`. Components own their dashboards in their own namespaces, so installing or removing a platform component updates the available dashboard set without changing the Grafana release.

Start with the Kubernetes global, namespace, or node views when the affected service is not yet known. Use the component dashboard after narrowing the problem to a specific subsystem, then correlate the metrics with Loki logs or Tempo traces.

## BullSequana AI 1.3 dashboard inventory [#bullsequana-ai-13-dashboard-inventory]

### Cluster and storage [#cluster-and-storage]

* `Kubernetes / Views / Global`
* `Kubernetes / Views / Namespaces`
* `Kubernetes / Views / Nodes`
* `Kubernetes / Views / Pods`
* `Kubernetes / System / API Server`
* `Kubernetes / System / CoreDNS`
* `Kubernetes / Persistent Volumes`
* `Kubernetes / Storage Usage`
* `Namespace Monitoring`
* `CNPG`
* `CloudNativePG`

The two PostgreSQL dashboards are separate operational views: `CNPG` focuses on the deployed database cluster, while `CloudNativePG` covers operator and cluster-level telemetry.

### Networking, security, and policy [#networking-security-and-policy]

* `Envoy Gateway`
* `cert-manager`
* `External Secrets Operator`
* `Istio Service Mesh`
* `Kyverno Policy Engine`
* `Keycloak capacity planning dashboard`
* `Keycloak troubleshooting dashboard`
* `OpenBao`
* `OpenFGA`

### Delivery and workflows [#delivery-and-workflows]

* `ArgoCD`
* `Argo Workflows Metrics`
* `Argo Events EventBus`
* `Temporal Server Metrics`

### Observability and hardware [#observability-and-hardware]

* `Prometheus`
* `Grafana Alloy`
* `Loki Kubernetes Logs`
* `NVIDIA DCGM Exporter`

### AI and data services [#ai-and-data-services]

* `KServe Controller`
* `KServe LLMInferenceService`
* `Kubeflow Pipelines`
* `LiteLLM Proxy`
* `MLflow Tracking`
* `Milvus - Data Path`
* `Milvus - Query Path`
* `Strimzi Kafka Operator`

## Deployment notes [#deployment-notes]

Grafana deploys as part of the `kube-prometheus-stack` chart in the `grafana` namespace at sync wave 9 in the common tier. Grafana uses the CNPG PostgreSQL cluster for its own state and authenticates through Keycloak OIDC.

## Interacts With [#interacts-with]

* `Prometheus`, which provides the platform metrics data source.
* `Grafana Loki`, which provides the platform log data source.
* `Grafana Tempo`, which provides the platform trace data source.
* `Keycloak`, which provides OIDC authentication and role mapping.
* `PostgreSQL`, which stores Grafana state and configuration.
* `Platform components`, which provision their dashboards through labeled `ConfigMap` resources.