Feature Requests Grouping checks / tagging
Under Review
Ability to create group of checks or tag them to ease search and filtering.
Support
Created on September 01, 2015 · Last update on July 16, 2024 Ability to create group of checks or tag them to ease search and filtering.
16 Comments
It would be great if this grouping could use tags
There's no plan to add a new feature for this, but it's already possible to do basic grouping by using the check alias (e.g. "Client A / Site 1"), this way you can sort by Alias in your dashboard and have your checks grouped by client/project/etc.
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 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.
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)
Sorting and filtering by customer, production/staging, framework version, server type, etc.
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.
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
Gruppierung von Monitoren (z.B. über Labels)
Tagging would be a great idea, able to group customers websites by tags in the api would be a great plus
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.
@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.
Tagging would make it easier to group and sort customers. I've attached an example of how it would help for our use case.
Filtering by server name perhaps
I'd also find it useful to specify settings to a group, for example for dev-server group interval would be 1 hour and notifications would go to developer slack/telegram/etc.
When you add a server to dev-group it would automatically get those settings. This would also help to make sure all services have the correct settings as they would be coming from the group.
We monitor services for multiple internal organisations/business units and it would be nice to filter with those views etc.
Grouping for customers or projects
Sign in to comment