search

fiveai / Cachet

📛 An open source status page system for everyone.
https://cachethq.io
BSD 3-Clause "New" or "Revised" License
101 stars 28 forks source link

Enhancement : multi-components incident #37

Open Yves911 opened 3 years ago

Yves911 commented 3 years ago

Hello,

At this stage an incident can be declared only at a component level.

It could be great to be able to declare an incident that belongs to several components (for example a power outage that could affect several machines/components at the same time).

So instead of having a drop-down list of components, would be great if we can tick those we want to mark as linked to incident.

Cheers

sedan07 commented 3 years ago

@Yves911 thanks for this. I think this would be useful, need to have a look to see how much work this will be.

seanhoughton commented 3 years ago

We just had a major power outage that took out ~50 services and it would have been really nice to be able to flag them all as affected by the same issue/incident. On the other hand, the services were not all restored at the same time so being able to individually flag components that were affected as part of the same incident as "operational" would be needed.

In other words, I can see how this feature might seem simple at first but could start to become tricky if you want to capture the details of a more complex outage.

kcan commented 3 years ago

maybe it can be a feature to group the incidents together afterward all incidents are resolved manually, then the title of the group is the incident that causes the outage. And during the incident outage period, each component can have it’s own incident and status change individually.

Get Outlook for iOShttps://aka.ms/o0ukef

From: Sean Houghton @.> Sent: Monday, August 9, 2021 9:24:57 PM To: fiveai/Cachet @.> Cc: Subscribed @.***> Subject: Re: [fiveai/Cachet] Enhancement : multi-components incident (#37)

We just had a major power outage that took out ~50 services and it would have been really nice to be able to flag them all as affected by the same issue/incident. On the other hand, the services were not all restored at the same time so being able to individually flag components that were affected as part of the same incident as "operational" would be needed.

In other words, I can see how this feature might seem simple at first but could start to become tricky if you want to capture the details of a more complex outage.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/fiveai/Cachet/issues/37#issuecomment-895480432, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAXIAOLEM5LWLFVKTQ3HT43T4ATQTANCNFSM4XUWHA3Q.

YannickFavre commented 2 years ago

Hello, this feature would be very interesting in the case of many subscribers. The idea is to not send one mail per component.

Is this feature planned in the 2.6 ?