> For the complete documentation index, see [llms.txt](https://docs.monspark.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monspark.com/website-monitoring/working-with-monitors/deleting-monitors.md).

# Deleting Monitors

Delete monitors that are no longer needed. You can easily delete your desired monitors either one by one or in bulk.

### Deleting a single monitor

{% @arcade/embed flowId="txE3X5EqNGCeXhLg8P87" url="<https://app.arcade.software/share/txE3X5EqNGCeXhLg8P87>" %}

* Find the monitor that you want to delete.
* Click the monitor actions button on the top-right of the monitor.&#x20;
* &#x20;Select “delete” action.
* Confirm your action and the monitor will be deleted.

***

### Deleting monitors in bulk

{% @arcade/embed flowId="lAcgP2gaPDC4glmc4WQn" url="<https://app.arcade.software/share/lAcgP2gaPDC4glmc4WQn>" %}

* Select the monitors you want to delete.&#x20;
* You can choose monitors either by clicking on boxes individually or by choosing to select all monitors option.&#x20;
* After choosing your desired monitors, click on the actions button.&#x20;
* Click on delete selected monitors.&#x20;
* Confirm your choice.


---

# 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.monspark.com/website-monitoring/working-with-monitors/deleting-monitors.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.