> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.12/development/flow-studio/monitoring/applications.md).

# Applications

To be able to monitor an application in the Applications sub tab, tick the Monitored checkbox in the metadata panel.&#x20;

<div align="left"><img src="https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-p-Y6jMZstljnKL4S_%2F-M-p-xtdkNF2KOsl3yNe%2Fhelp_root_monitoring_applications_metadatamonitired.png?alt=media&amp;token=ec32a0a4-eaf8-4797-962c-95c8b910117d" alt=""></div>

In Monitoring tab, user can select Applications sub tab and select workflow by clicking Choose application dropdown.\
&#x20;Application process Ids will be registered and displayed in table with Start Time and End Time details. The process ID is a link, that pressed will bring User to specified process in Tasks overview.

Clicking button: ? Refresh, user will reload results and get actual data ? Open Workflow, user will open selected workflow in Application main tab.&#x20;

![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-p-Y6jMZstljnKL4S_%2F-M-p01J1n366hduXcR0A%2Fhelp_root_monitoring_applications_monapps.png?alt=media\&token=ff0d026d-7937-4941-8b3d-4556e50715f8)


---

# 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://help.novacuraflow.com/6.12/development/flow-studio/monitoring/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.
