> For the complete documentation index, see [llms.txt](https://docs.connect.jfrog.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.connect.jfrog.io/features-new-ui/tools/get-alerts/create-monitored-process.md).
# Create Monitored Process
Monitor a process and create alerts for conditions you define.
You can monitor a process by entering the software binary name. Connect monitors the given application name by searching for the currently running process with a similar name on the connected device.
In most cases, the software binary name is the same as the executable file name. Below are some examples. \
\
`app.py` - For a Python application, enter the main Python application file name that is being executed by Python.\
`app` - For an executable binary file, enter the binary file name.\
`app.sh` - For a Bash file, enter the Bash file name.\
`mysql` - For a ready-service, enter the service name.
{% hint style="success" %}
**Tip**: In case of monitoring issues, it is recommended to enter the full path of the running application, for example: `/home/device-app/app.py`.
{% endhint %}
To create a new monitored process, do the following:
1. In the left navigation tree, go to **Alerts**>**Configuration** **tab**>**Processes**>**New Process**.
2. In the Create New Monitored Process wizard, enter the **Binary Name** and click **Next**.
3. Select the devices to be monitored. These can be in a specific group, specific devices you choose, or devices meeting some other criteria that you define. Click **Next**.
4. View the Summary, which shows the number of devices that will monitored, and click **Start Monitoring**.
## What's Next?
Learn how to [view, edit, and delete monitored processes](/features-new-ui/tools/get-alerts/create-monitored-process/view-monitored-processes.md).
---
# 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.connect.jfrog.io/features-new-ui/tools/get-alerts/create-monitored-process.md?ask=&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.
