Cachet: Add new component status for ongoing maintenance (e.g. UNDER MAINTENANCE)
During discussions in #2044 we came across the idea to add another status for components to be able to mark the component as "under maintenance". This would ease our maintenance workflow:
- Schedule a maintenance
- When maintenance is started set the status to "UNDER MAINTENANCE"
- When maintenance is done reset the status
We're also creating incidents via a checking service and so we are able to skip incident creation when the component is under maintenance.
stipx
All 27 comments
I think the way I'm going to handle this is to add a new status and at the same time make the status names configurable 馃挜
jbrooksuk
on 15 Aug 2016
Hi,
any news on this? We eagerly await this feature to get our workflow clean.
stipx
on 4 Oct 2016
@stipx I've rewritten the scheduled maintenance system today, but need to finish it off so that components can be modified too. Then we'll be there!
jbrooksuk
on 30 Oct 2016
Okay, so there won't be a new status specifically for this, instead the component status will be changed to say "Under maintenance" or whatever we decide on 馃憤
jbrooksuk
on 4 Dec 2016
All we need is a way of selecting affected components in the dashboard now.
jbrooksuk
on 4 Dec 2016
Look forward to this, also i noticed there was no way to set a specific component to "maintenance" which i thought was odd, so this will be a welcome feature.
shaun-ba
on 27 Dec 2016
Really looking forward to custom status names, hope that feature can be included in a v2.4 release potentially as well as originally mentioned!
Hunterm267
on 28 Dec 2016
You can rename your status-names in /resources/lang/YOUR-LANGUAGE/cachet.php in line 17-20.
niclasreich
on 2 Jan 2017
But I do not want to rename the status. I would like to have another one. The current states with "Operational", "Performance Issues", "Partial Outage" and "Major Outage" are all in use.
stipx
on 3 Jan 2017
Adding a new status is a little harder because we have validation in place.
jbrooksuk
on 3 Jan 2017
Another vote for additional statuses. In our case we would like an "At Risk" status between "Operational" and "Performance Issues".
For example, when grid power has failed and switched to generators or any other part of the service is running on a failover system, the component would be considered "At Risk" of failure. Some may consider this a "partial outage" but as far as our customers are concerned, there is no outage, there is just a greater risk of an outage occurring than usual.
mhayes14
on 21 Jan 2017
@mhayes14 I see what you're saying... 馃
jbrooksuk
on 30 Jan 2017
Another vote for configurable statuses! Having them configurable gives you the freedom to have as many and name statuses as you want.
MarkL4YG
on 19 Apr 2017
+1 for more statuses and configurable names + colors!
julianschiavo
on 19 Jun 2017
Thoughts...
We'd setup default component and incident statuses within a configuring table:
id | name | slug | type | status_id
1 | Unknown | unknown | components | 0
2 | Operational | operational | components | 1
3 | Performance Issues | performance-issues | components | 2
4 | Partial Outage | partial-outage | components | 3
5 | Major Outage | major-outage | components | 4
6 | Investigating | investigating | incidents | 1
7 | Identified | identified | incidents | 2
8 | Watching | watching | incidents | 3
9 | Fixed | fixed | incidents | 4
This means incidents and components can have different statuses. We'd do this as part of the migration I guess, but it would default English versions.
We'd need a dashboard to manage these statuses too...
jbrooksuk
on 17 Jul 2017
That's very interesting! Maybe also add a column for component coloring.
I'd love to test ;)
MarkL4YG
on 18 Jul 2017
Just started using Cachet and really need this feature added so that I can have a deprecated status. If we're moving a service out and it will no longer be available, we want to communicate that without having it look like its down by error.
phutchins
on 26 Jul 2017
馃憤
It's being worked on @phutchins :)
jbrooksuk
on 26 Jul 2017
+1
felipelalli
on 8 Feb 2018
Awesome! Thanks for the update!
phutchins
on 9 Feb 2018
Just wanted to open a feature request for this.
It would be awesome to have this feature released with 2.4. It is also required to be able select components that will be affected by the maintenance work.
Thanks guys!
ghost
on 3 Jul 2018
I've been thinking about this a bit more.
Would it make sense that as soon as a scheduled maintenance becomes active, the component needs to simply change the status to "Under Maintenance"?
jbrooksuk
on 4 Jul 2018
The important thing here is that if a schedule attaches to a component, then it will always be under maintenance, it wouldn't be a choice.
jbrooksuk
on 4 Jul 2018
@jbrooksuk I would say that opening up the status implementation to allow more and customized statuses would be a more sophisticated though complicated approach.
One could a "set component status to:" field to the incident dialog be the incident planned or unplanned with the selected status becoming active with the incident.
MarkL4YG
on 4 Jul 2018
Is there any way, today, to add a single custom status without tweaking the code too much? Anyone done that?
jlcd
on 2 Dec 2018
@jlcd Not that I am aware of. But you could just rename one of the predefined ones?
Otherwise, you could try to figure out how the statuses are implemented. Surely this will reveal how to add custom statuses atm.
MarkL4YG
on 2 Dec 2018
Any progress on this? @jbrooksuk
Blizzard098
on 2 Nov 2019
Related issues
Phelzier
路
7Comments
thomvaill
路
7Comments
brianjking
路
4Comments
sapk
路
8Comments
jbrooksuk
路
5Comments
Most helpful comment
I think the way I'm going to handle this is to add a new status and at the same time make the status names configurable 馃挜