# Custom Alert Rules for Sythetics

**URL:** <https://discuss.elastic.co/t/custom-alert-rules-for-sythetics/359728>\
**Category:** Synthetics\
**Created:** [May 17, 2024, 5:09pm UTC](https://discuss.elastic.co/t/custom-alert-rules-for-sythetics/359728 "2024-05-17T17:09:42Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![DougR](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dougr/32/48095_2.png) [@DougR](https://discuss.elastic.co/u/DougR)\
**Post date:** [May 20, 2024, 6:22pm UTC](https://discuss.elastic.co/t/custom-alert-rules-for-sythetics/359728/2 "2024-05-20T18:22:32Z")

</div>

I asked basically this same question a few days ago, you can see the answer I was given [here](https://discuss.elastic.co/t/elastic-synthetics-alerts-in-the-same-workspace-to-different-teams/359477/2).

I am successfully sending alerts from the the same workspace to different endpoints based on workspace name and tags as follows:

```auto
data_stream.namespace:"my_namespace" AND tags:("my_app" AND "my_env")

```

The one issue I'm having is that the uptime rules don't appear to respect the `alert.status.enabled` switch in my tests. I'm planning on resolving this in the short term by ignoring anything with a `disable_alerts` tag set, but I'm hoping there's a better solution.

---

_[View the full topic](https://discuss.elastic.co/t/custom-alert-rules-for-sythetics/359728)._