> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/gettingstarted/devops-portal/runtime-info.md).

# Runtime Info

The **Runtime Info** section provides general information about the selected Runtime and gives insight into the technical status of the environment.

The landing page contains the following topics:

* General Runtime Information
* Environment SMTP Settings
* Pod Overview (Runtime Components & Resource Usage)

## General runtime information

At the top of the page, basic information about the selected Runtime is displayed.

* **Name** \
  The name of the Runtime environment
* **Mode** \
  Shows cluster type, Staging or Live.
* **Base URL** \
  The primary URL of the Runtime (can be used as CNAME target for custom hostnames)
* **Runtime Version** \
  The currently deployed WEM Runtime version

## Settings

This section currently only shows the SMTP settings, these settings define the default outgoing mail configuration for applications running on this Runtime.

Selecting the SMTP settings button opens up the follow window: 

<figure><img src="/files/nfvlZFZF4tafSDLvo8oN" alt=""><figcaption></figcaption></figure>

If configured at Runtime level, applications can inherit these settings unless they explicitly override them with application-specific SMTP configuration.

Use environment-level SMTP when:

* Multiple applications share the same mail configuration
* Centralized mail configuration is preferred

If SMTP is configured per application, those settings take precedence over the environment-level configuration. You can find more information about setting up SMTP settings on a project level on this page: [SMTP Settings](/platform/wemmodeler/project-settings/smtp-settings.md).&#x20;

## Pod Overview

A pod represents a deployed component of the WEM Runtime installation.\
These components together form the complete Runtime environment.

By selecting a component, you can view its:

* CPU usage
* Memory usage


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.wem.io/platform/gettingstarted/devops-portal/runtime-info.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.