tnolet
commented
1 year ago @andreas-svendby-adsk we have been actively discussing this internally, as we do the same thing: we monitor our staging and production with essentially the same checks. Now with our CLI https://github.com/checkly/checkly-cli the need becomes more pressing even. We do however see two different scopes:
- Projects. This is in many cases a Git repo. Doesn't necessarily have to be, but it makes the most sense. This would be "webapp" or "api backend" etc.
- Environments These are your deployment environments: dev, staging, production etc.
One Project's checks can be targeted at multiple environments, where you can set environment variables per environment. E.g. PASSWORD=xxxx
Does this match your workflow?
Is your feature request related to a problem? Please describe. We are running the same checks against different, duplicate environments. With the current UI where we can only have groups, and only one level of groups, it can become harder to reason around the checks.
Describe the solution you'd like Having workspaces/projects per environment would let us group checks in a logical way. It could also give a realistic overview of the passed/degraded/failing checks, as that could be per workspace/project. It would also enable things like having code snippets/alert rules etc specific to a workspace/project.
Describe alternatives you've considered Having multiple levels of grouping could somewhat alleviate the issue, but the overview of passed/degraded/failing checks would not be as useful, as it would not be possible to know if the issue is in multiple environments or isolated to one environment.
We could also set up multiple organisations, but that is something we want to avoid. Logically it isn't separate organisations, and we want to have the same payment/contact/users/access control etc.