> For the complete documentation index, see [llms.txt](https://docs.seldon.ai/seldon-enterprise-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seldon.ai/seldon-enterprise-platform/operations/healthcheck.md).

# Health Check

Seldon Enterprise Platform has a built-in health check that aims to monitor the availability of its surrounding ecosystem as well as troubleshoot problems when they arise. This can be done as an intermediary step before checking the logs or contacting us.

## Where to find the Health Check Monitor

You can find the health check by clicking on the user icon on the top right of the screen.

![user-header](https://1921172648-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvLlcdnP8YnaIFsv8EiMA%2Fuploads%2Fgit-blob-41b8492671dedad8d076cc87b9dc0b230b05a5c7%2Fuser-header.png?alt=media)

Then you can select *Health Check*.

![healthcheck\_menu.png](https://1921172648-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvLlcdnP8YnaIFsv8EiMA%2Fuploads%2Fgit-blob-f67d0ea805ca2f55583fe42e7910e5bc62de2185%2Fhealthcheck_menu.png?alt=media)

Afterwards, you should see a page like this:

![healthcheck.png](https://1921172648-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FvLlcdnP8YnaIFsv8EiMA%2Fuploads%2Fgit-blob-ee11677c08e100c41a434d66d3cb92c3113d3f2e%2Fhealthcheck.png?alt=media)

## Health Check Components Explained

{% hint style="info" %}
**Note**: The health check is still experimental; if you have any issues, please contact us.
{% endhint %}

| Dependency       | What does the check do?                                                                                                                                                                  |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Alertmanager`   | - pings Alertmanager's internal health endpoint                                                                                                                                          |
| `Elasticsearch`  | - pings Elasticsearch's internal health endpoint                                                                                                                                         |
| `Keycloak`       | <p>- checks if OIDC provider is available<br>- if the auth url is correctly configured<br>- also adds (as an info) if a user provider is available</p>                                   |
| `Knative`        | <p>- checks if Knative Eventing CRDs<br>- and Knative Serving CRDs are installed<br>- and if their pods are running</p>                                                                  |
| `Postgres`       | <p>- checks first if Postgres is enabled<br>- if it is enabled, the test will try to run a simple query</p>                                                                              |
| `Prometheus`     | - pings Prometheus' internal health endpoint                                                                                                                                             |
| `Seldon Core v1` | <p>- checks if Seldon Core v1 CRDs are installed<br>- and if the <code>seldon-controller-manager</code> (in Seldon Core v1 <code>namespace</code>) deployment in Kubernetes is ready</p> |
| `Seldon Core v2` | <p>- checks if Seldon Core v2 CRDs are installed<br>- and if the <code>seldon-controller-manager</code> (in Seldon Core v2 <code>namespace</code>) deployment in Kubernetes is ready</p> |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.seldon.ai/seldon-enterprise-platform/operations/healthcheck.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.