> For the complete documentation index, see [llms.txt](https://tmediadocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tmediadocs.telcobridges.com/other-pages/cdr-radius-and-applications/status-menus-applications.md).

# Status Menus:Applications

#### ***Applies to version(s): v2.5, v2.6.***

General and detailed status information about the applications that are run by one or more host machine(s) is accessible from the **Applications** tab of the Global-->Status menu.

![Toolpack v2.5 Navigation Panel Status](https://docs.telcobridges.com/w/images/3/3c/Toolpack_v2.5_Navigation_Panel_Status.png)

### General view

The general view, shown below, lists the applications, and their current general status (ready, fault, not running. This window also provides a count of all applications with ready or fault status.

![Toolpack v2.5 Status Applications](https://docs.telcobridges.com/w/images/2/26/Toolpack_v2.5_Status_Applications.png)

### Detailed view

A more detailed description of each application can be viewed by following the appropriate link in the general window (shown above).

The detailed status screen, shown below, lists the states of the application, its name, the host machine and the location of the application on the host.

From this detailed view, **the Oam target state may be changed**. To modify the Oam target state of an application:

* Select a state from the **Oam target state** combo box.
* Click **Apply States** to change the states.

![Toolpack v2.5 Status Individual](https://docs.telcobridges.com/w/images/5/52/Toolpack_v2.5_Status_Individual.png)


---

# 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://tmediadocs.telcobridges.com/other-pages/cdr-radius-and-applications/status-menus-applications.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.