Configuration Management

[lee5i3]

Describe the feature request

Any plans to make the configuration a bit more manageable when its getting large. We are having a lot of checks in our configuration and it is starting to become difficult to manage, even with yaml anchors

Any plans to allow configuration changes via UI
Or maybe even a custom CRD rather than having everything in the yaml

Our issues also start when every application seems to have different configuration, not just the checks but who they are being sent to, often we have checks that go to different people so we end up having to create multiple different anchors

Why do you personally want this feature to be implemented?

Would be nice is to have an area to create alerts and endpoints, possible to be done by creating CRDs or even saved into a database that gatus uses. This would also solve any invalid configuration syntax, which often breaks gatus when we mistype a configuration.

This also helps for users that are less experienced with YAML structure to have a more manageable way to create endpoints using a more UI based than YAML based.

How long have you been using this project?

We've been using gatus in production for just over a year

Additional information

No response

[TwiN]

UI based configuration management is not something I'm interested in supporting.

As for CRDs, there were plans to work on a k8s operator at some point, I just haven't had the time to work on it yet.

You can use multiple configuration files as well as YAML anchors for now though, which should help with keeping the configuration more manageable.

[lee5i3]

I did not realize we could have multiple configurations, will look into that, might be a bit easier to manage in separate files, as our configuration is getting pretty large

Thanks!

[TwiN]

Basically you can specify a folder for your configuration instead of a single file, and all yaml files within that folder are merged using https://github.com/TwiN/deepmerge into one big configuration. This allows you to do things like splitting endpoints configs by group (one file per group), or having one configuration for endpoints, one for suites, one for alerting, etc.