# Already deleted monitor is reporting monitor status to elasticsearch
**URL:** https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936
**Category:** Synthetics
**Created:** [May 8, 2025, 11:29am UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936 "2025-05-08T11:29:17Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@niecore](https://discuss.elastic.co/u/niecore)
#### Post date: [May 8, 2025, 11:29am UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/1 "2025-05-08T11:29:17Z")
I deleted a synthetics monitor but still receive new monitor results in the synthetics-\* datastream. The monitor is also still visible in the old uptime app and the monitor is triggering alerts that are configured based on monitor tags. I can not delete the monitor via the ui, because its not visible and the synthetics app and I can not delete the monitor via the kibana api.
I am running elastic stack version 8.18.1.
How to get rid of the leftover monitor?
---
### Author:  [@Jcesar9100](https://discuss.elastic.co/u/Jcesar9100)
#### Post date: [May 8, 2025, 11:43am UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/3 "2025-05-08T11:43:22Z")
Have you tried deleting it directly from the index? If you are not familiar with the terminal, you can do this directly from Kibana via Devtools. First, you apply a GET to check the permanence of the index you want to remove.
# First, identify the exact monitor ID with GET
```auto
GET /synthetics-*/_search
{
"query": {
"term": {
"monitor.id": "your-monitor-id"
}
}
}
```
# Then delete all documents for that monitor
```auto
POST /synthetics-*/_delete_by_query
{
"query": {
"term": {
"monitor.id": "your-monitor-id"
}
}
}
```
Or try deleting through the Fleet API:
```auto
POST /api/fleet/agent_policies/delete_monitors
{
"monitorIds": ["your-monitor-id"]
}
```
---
### Author:  [@niecore](https://discuss.elastic.co/u/niecore)
#### Post date: [May 8, 2025, 11:49am UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/4 "2025-05-08T11:49:15Z")
Deleting the data is not the problem. I need the monitor to stop reporting new data.
The endpoint `/api/fleet/agent_policies/delete_monitors` does not exist.
---
### Author:  [@Jcesar9100](https://discuss.elastic.co/u/Jcesar9100)
#### Post date: [May 10, 2025, 5:03pm UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/5 "2025-05-10T17:03:59Z")
Sorry for asking again, did you remove the index or remove the policy? Because removing the index will cause it to re-execute, you must remove the policy and restart the agent to unlink the requests.
---
### Author:  [@niecore](https://discuss.elastic.co/u/niecore)
#### Post date: [May 12, 2025, 8:12am UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/6 "2025-05-12T08:12:01Z")
I am using elastic synthetics monitoring and therefore no agents and no agent policies.
The monitor was removed via the synthetics app of kibana.
---
### Author:  [@shahzad31](https://discuss.elastic.co/u/shahzad31)
#### Post date: [May 20, 2025, 9:44am UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/7 "2025-05-20T09:44:59Z")
@niecore can you please share monitor ID and from which location the monitor is running from?
---
### Author:  [@niecore](https://discuss.elastic.co/u/niecore)
#### Post date: [May 20, 2025, 10:01am UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/8 "2025-05-20T10:01:24Z")
europe-west3-a, da1c3a35-ca90-464d-a9ae-eb442ec644d5
---
### Author:  [@shahzad31](https://discuss.elastic.co/u/shahzad31)
#### Post date: [May 20, 2025, 11:49am UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/9 "2025-05-20T11:49:11Z")
@niecore thank you providing additional info, we are investigating it now.
---
### Author:  [@shahzad31](https://discuss.elastic.co/u/shahzad31)
#### Post date: [May 20, 2025, 12:13pm UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/10 "2025-05-20T12:13:51Z")
@niecore as a follow up question, are you able to add new monitors in that location and are those running successfully?
---
### Author:  [@niecore](https://discuss.elastic.co/u/niecore)
#### Post date: [May 20, 2025, 12:28pm UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/11 "2025-05-20T12:28:54Z")
@shahzad31 thanks for helping out here! Yes I am able to configure new monitors which are running correctly.
---
### Author:  [@shahzad31](https://discuss.elastic.co/u/shahzad31)
#### Post date: [May 20, 2025, 3:04pm UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/12 "2025-05-20T15:04:19Z")
@niecore can you please run this query and see if the monitor still exists as saved objects
```auto
GET .kibana*/_search
{
"size": 10000,
"query": {
"bool": {
"filter": [
{
"term": {
"type": "synthetics-monitor"
}
},{
"term": {
"synthetics-monitor.config_id": "da1c3a35-ca90-464d-a9ae-eb442ec644d5"
}
}
]
}
}
}
```
---
### Author:  [@shahzad31](https://discuss.elastic.co/u/shahzad31)
#### Post date: [May 20, 2025, 3:25pm UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/13 "2025-05-20T15:25:19Z")
I noted in past you have been hitting the limit on number of monitors you can run on a location, if you need to increase limit you can raise a support ticket and team should be able to help you with that.
---
### Author:  [@niecore](https://discuss.elastic.co/u/niecore)
#### Post date: [May 21, 2025, 5:44am UTC](https://discuss.elastic.co/t/already-deleted-monitor-is-reporting-monitor-status-to-elasticsearch/377936/14 "2025-05-21T05:44:42Z")
The monitor seems to be not available in the saved objects:
```auto
#! this request accesses system indices: [.kibana_8.4.1_001, .kibana_8.4.2_001, .kibana_8.5.0_001, .kibana_8.6.0_001, .kibana_8.8.0_001, .kibana_alerting_cases_8.8.0_001, .kibana_analytics_8.8.0_001, .kibana_blob_storage, .kibana_entities-definitions-1, .kibana_ingest_8.8.0_001, .kibana_security_session_1, .kibana_security_solution_8.8.0_001, .kibana_task_manager_8.4.1_001, .kibana_task_manager_8.4.2_001, .kibana_task_manager_8.5.0_001, .kibana_task_manager_8.6.0_001, .kibana_usage_counters_8.17.0_001], but in a future major version, direct access to system indices will be prevented by default
{
"took": 112,
"timed_out": false,
"_shards": {
"total": 48,
"successful": 48,
"skipped": 47,
"failed": 0
},
"hits": {
"total": {
"value": 0,
"relation": "eq"
},
"max_score": null,
"hits": []
}
}
```
It also stopped reporting at May 20, 2025 @ 23:48:54.147.
Thanks for your help!