Ability to create group for gathering checks
What would this be useful for?
Bram V commented
@Adrien: We also need this functionality. We will be adding a lot more checks and it would help if we could group them by customer / department.
Olaf Lederer commented
I would use the group label for the server name from the checked website. This way I know which server I need to check for log files, frozen processes, database login.
Sean Valentine commented
Tagging would be a great idea, able to group customers websites by tags in the api would be a great plus
BITBEE Solutions GmbH commented
Gruppierung von Monitoren (z.B. über Labels)
Arnaud Lapiere commented
Additional use case (Am I the only one doing this ? ) I have several probes for important websites, with text string check, so I can make sure there is no regression .
(It already happened to me I had the homepage working, but no others, due to Wordpress permalinks issue) --> grouping probes of the same website in a group/tag make sense, of course
The first comment touched on this, but this is important (if slightly obvious):
What we really need is tags, not groups, since any simple or complex groupings can be trivially implemented (on the client side) on top of tags.
Sorting and filtering by customer, production/staging, framework version, server type, etc.
Ok I see, about the slack channels though @Matt this is now possible to have multiple slack channels and select were each check's notification go to (released about 2 months ago)
Matt Heerema commented
It would help to show patterns to diagnose reasons for downtime. Example, I have multiple servers housing these sites. It would make sense for me to see them all as a bundle. If all of the sites within a group were down, it would indicate a server issue.
Also, by "gathering checks" I meant primarily in the realm of slack notifications. One groups notifications could go to one slack channel, another group to another channel. Right now the only way to accomplish this is by having multiple updown accounts.
sense-design | online solutions commented
Customers may have multiple projects so it would be nice to group them and have them sorted by the customer and not the name of the project. Otherwise you have to always use a project prefix like "customer name: project name"
It would be great if this grouping could use tags