Use a check in multiple components on a single status page
I'd like to add a check in multiple different groups within a single status page.
For example, i have a check that checks the UserIdentification service.
If the UserIdentification service is down, it will affect Authentication and Order Processing (for example)
I'd like to have groups for Authentication and Order Processing on the status page and have the check apply to both of those so that both are listed as affected when the User Identification service is affected, so that I can provide better feedback on the overall effects of the outage rather than just reporting on the check itself.
At present, the only way to do this is to duplicate the checks, which then means managing multiple instances of the same check independently, increasing admin overhead.
Log in to comment and vote
Comments3
Amaranth Raindrop
Sep 10, 2024
Pinned@Fuuse Fuuse I have confirmed with Engineering that this issue can be fixed and we will allow individual checks to be assigned to multiple groups. I have created a story for this and I anticipate it will done in a few weeks. We will keep you posted here. Thanks! Jonathan
Amaranth Raindrop
Aug 31, 2024
Hi Fuuse Devs - I actually wanted to drill into this one more level. See below screenshots. You are referring to have 2x different groups on the status page and using the same component name in both backed by the same individual check correct? Currently the UI doesn’t allow this which I am guessing is the error you are receiving is that accurate? Just want to confirm this quickly and see if we can get this fixed relatively quickly.
Sapphire Mongoose
Aug 30, 2024
Hi Fuuse Devs! Thanks for reaching out and providing this feedback. Tom here; I'm a Product Manager at Uptime. I understand your use case, and I agree that using the same Check in different groups would be helpful if that Check relates to various services. We plan on many improvements to our Status Page feature in upcoming releases. I can't give an exact timeline, but this is undoubtedly a function we will discuss and hopefully add in the future.