larssb / HealOps

A monitoring and healing framework. It uses Pester tests (TDD) to determine the state of an IT system entity. Then, if the entity is in a faulted state HealOps will try to repair it. All along HealOps reports metrics to a backend report system and HealOps status is sent to stakeholders. In order to e.g. trigger alarms and get on-call personnel on an issue that could not be repaired.

Home Page:https://healops.readthedocs.io/en/latest/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Consider supporting YML for the HealOps config file.

larssb opened this issue · comments

Use a JSON schema

Would be great to have/do in order to ensure conformance to what is needed by HealOps and a HealOpsPackage. And making it easier for a developer of a HealOpsPackage to know that they are doing things as they are supposed to.

(or if YML is chosen a schema fitting that format).

Consider supporting YML for the config files.
The foremost reason is to get the option of commenting on the lines in the configuration file. Besides, it heightens the readability of the configuration file.

Downsides:

  • Adds an extra pre-requisite to HealOps. powershell-yaml
  • And code work to incorporate it.