# Assign kibana alert running on a specific instance
**URL:** https://discuss.elastic.co/t/assign-kibana-alert-running-on-a-specific-instance/348704
**Category:** Kibana
**Created:** [December 6, 2023, 7:28am UTC](https://discuss.elastic.co/t/assign-kibana-alert-running-on-a-specific-instance/348704 "2023-12-06T07:28:39Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@JT\_IGS](https://discuss.elastic.co/u/JT_IGS)
#### Post date: [December 6, 2023, 7:28am UTC](https://discuss.elastic.co/t/assign-kibana-alert-running-on-a-specific-instance/348704/1 "2023-12-06T07:28:39Z")
There are multiple kibana instances connecting to same ES cluster:
kibana1 -\> elasticsearch \<- kibana2
After setting kibana alerts, found that kibana alerts run on random instance (1/2).
While i have a need to run rule on a specific instance.
Before kibana 8, using kibana.index as legacy multi tenancy could resolve the problem.
In kibana 8, this is migrated to kibana space but as both instance could access all space that is no difference as one space.
---
### Author:  [@bhavyarm](https://discuss.elastic.co/u/bhavyarm)
#### Post date: [December 27, 2023, 11:11pm UTC](https://discuss.elastic.co/t/assign-kibana-alert-running-on-a-specific-instance/348704/2 "2023-12-27T23:11:58Z")
@Brandon_Kobel / @mikecote can we please get some help here?
Thanks,
Bhavya
---
### Author:  [@JT\_IGS](https://discuss.elastic.co/u/JT_IGS)
#### Post date: [December 28, 2023, 3:57am UTC](https://discuss.elastic.co/t/assign-kibana-alert-running-on-a-specific-instance/348704/3 "2023-12-28T03:57:56Z")
thanks for replying.
from issue search online,
it seems after removing kibana index.
This is an issue could not be resolved unless with function update of kibana alert / rule
---
### Author:  [@mikecote](https://discuss.elastic.co/u/mikecote)
#### Post date: [December 28, 2023, 1:29pm UTC](https://discuss.elastic.co/t/assign-kibana-alert-running-on-a-specific-instance/348704/4 "2023-12-28T13:29:16Z")
Hi @JT_IGS, I can confirm that this isn't possible at this time given the system design. All the Kibana instances are designed to run background tasks.
We would need to further enhance the dedicated node roles functionality for this to be possible. In the meantime, it may be possible to achieve something with two separate Kibana instances and cross cluster searching: [Search across clusters | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-cross-cluster-search.html) but it's not guaranteed to work for your use case.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [January 25, 2024, 1:29pm UTC](https://discuss.elastic.co/t/assign-kibana-alert-running-on-a-specific-instance/348704/5 "2024-01-25T13:29:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.