# Index name that Uptime look for **URL:** \ **Category:** Synthetics\ **Created:** [February 27, 2020, 9:42am UTC](https://discuss.elastic.co/t/index-name-that-uptime-look-for/221198 "2020-02-27T09:42:40Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![leprovokateur](https://avatars.discourse-cdn.com/v4/letter/l/8e8cbc/32.png) [@leprovokateur](https://discuss.elastic.co/u/leprovokateur)\ **Post date:** [February 27, 2020, 9:42am UTC](https://discuss.elastic.co/t/index-name-that-uptime-look-for/221198/1 "2020-02-27T09:42:40Z")
Hi, I want to have different users not to be able to see all uptime data in the Uptime app. My approach would be to have different heartbeat instances creating indices with different names and set the permissions for the users appropriately. For which index names does the Uptime app look for? Best regards, Robert ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [February 27, 2020, 12:26pm UTC](https://discuss.elastic.co/t/index-name-that-uptime-look-for/221198/2 "2020-02-27T12:26:36Z")
heartbeat. ---
**Author:** ![leprovokateur](https://avatars.discourse-cdn.com/v4/letter/l/8e8cbc/32.png) [@leprovokateur](https://discuss.elastic.co/u/leprovokateur)\ **Post date:** [February 27, 2020, 12:28pm UTC](https://discuss.elastic.co/t/index-name-that-uptime-look-for/221198/3 "2020-02-27T12:28:00Z")
Is it possible to change this somehow? ---
**Author:** ![drewpost](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drewpost/32/46162_2.png) [@drewpost](https://discuss.elastic.co/u/drewpost)\ **Post date:** [February 27, 2020, 12:44pm UTC](https://discuss.elastic.co/t/index-name-that-uptime-look-for/221198/4 "2020-02-27T12:44:37Z")
Hi there. I'm the Product Manager for Uptime. Right now, no, it cannot be changed. That being said, we are actually working on this capability quite literally as I type this. I obviously can't commit to an exact release date but our hope it to get it into the next (7.7) release. As with any software project, that could change if any big issues come up but it's looking on target so far. ---
**Author:** ![jkambic](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jkambic/32/53306_2.png) [@jkambic](https://discuss.elastic.co/u/jkambic)\ **Post date:** [February 27, 2020, 10:37pm UTC](https://discuss.elastic.co/t/index-name-that-uptime-look-for/221198/5 "2020-02-27T22:37:54Z")
Heya @leprovokateur - there actually is a workaround you can use. In truth, the Uptime app [matches against a pattern](https://github.com/elastic/kibana/blob/7.6/x-pack/legacy/plugins/uptime/common/constants/index_names.ts#L8) like `heartbeat*`, so it is possible for you to achieve your goal, using either index names or aliases. You can create an index like `heartbeat-custom-1` and `heartbeat-custom-2`, and then grant whatever permissions you choose to roles for each, then assign those roles to your users. For example, below is a view of my Index Management screen when running as an admin: ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/8/58eef63bdea863a8e8d7841901335bec51dd64d7.png) I created two users, `User1` and `User2`, and assigned them each a custom role. `user-role-1` grants access to `heartbeat-hi-leprovokateur1*`, and `user-role-2` grants access to `heartbeat-hi-leprovokateur2*`. I'm running two instances of Heartbeat. They were both originally writing to `heartbeat-8.0.0...`, but I've modified them each to write to the other two indices. One of them is logging its location as `fairbanks` and the other as `harrisburg`. My first user can only see locations like `harrisburg`: ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/7/c73e6908c95c724e6eff419c9c3b483eefe97060.png) My second user can only see locations like `fairbanks`: ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/9/09cf37035db5abacd024500d232aabe76565e6a9.png) And this is what my super user sees (i.e. the data from all three `heartbeat*` indices combined: ![image](https://us1.discourse-cdn.com/elastic/original/3X/9/d/9dcb24cc4931d0e8421e109fd1296c1b6e0cec02.png) I think this accomplishes what you're looking for. Let me know if anything is unclear, cheers. ---
**Author:** ![Kim-Kruse-Hansen](https://avatars.discourse-cdn.com/v4/letter/k/f1d935/32.png) [@Kim-Kruse-Hansen](https://discuss.elastic.co/u/Kim-Kruse-Hansen)\ **Post date:** [March 2, 2020, 8:06pm UTC](https://discuss.elastic.co/t/index-name-that-uptime-look-for/221198/6 "2020-03-02T20:06:03Z")
Hi I am happy to see that you are removing hard-coded index names from uptime app. Will you accommodate cross cluster search - ccs also in the uptime app? Currently we are using our own dashboard for heartbeat because of the current implementation, so hope for news on topic. Regards Kim ---
**Author:** ![drewpost](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/drewpost/32/46162_2.png) [@drewpost](https://discuss.elastic.co/u/drewpost)\ **Post date:** [March 2, 2020, 8:20pm UTC](https://discuss.elastic.co/t/index-name-that-uptime-look-for/221198/7 "2020-03-02T20:20:47Z")
Hi Kim - that’s correct! It should ship at the same time. ---
**Author:** ![Kim-Kruse-Hansen](https://avatars.discourse-cdn.com/v4/letter/k/f1d935/32.png) [@Kim-Kruse-Hansen](https://discuss.elastic.co/u/Kim-Kruse-Hansen)\ **Post date:** [March 2, 2020, 8:46pm UTC](https://discuss.elastic.co/t/index-name-that-uptime-look-for/221198/8 "2020-03-02T20:46:48Z")
Awesome, we will be waiting for 7.7 😄 ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 26, 2020, 8:46pm UTC](https://discuss.elastic.co/t/index-name-that-uptime-look-for/221198/9 "2020-03-26T20:46:53Z")
This topic was automatically closed 24 days after the last reply. New replies are no longer allowed.