-
Notifications
You must be signed in to change notification settings - Fork 1
HealOps technologies
Why? PowerShell has often times been my go-to programming language. However, when I started out developing HealOps I initially considered if I should program it in PowerShell. The answer was yes. Because, around the same time I started developing HealOps PowerShell had begun being a somewhat stable cross-platform language. Available on MacOS, Linux and of course on Windows. So I thought, let me do this in the language I know the best.
Pester
Pester is a test-driven-development framework (TDD). Programmed in PowerShell and has a good following in the PowerShell community. It is also in continued development > https://github.com/pester/Pester. And most importantly, for this project. Suited the needs of HealOps.
PowerShellTooling
Is a self-developed propietary module. It contains many smaller helper functions used in various places in HealOps. Instead of having theese functions scattered around or copied into whatever new module I was developing, I made this PowerShell module, to be able to adhere to the DRY principle and to ease the workload of developing new PowerShell modules.
Find it here > https://github.com/larssb/PowerShellTooling (PSGallery is being considered).
Data derived from monitoring and healing IT services and their components with HealOps. Are supposed to be stored in a time-series backend. However, it is the goal that it should be possible to freely decide what type of time-series database backend to use.
It is also the idea that the stored data is to be visualized on a dashboard system like Grafana, Prometheus or the like. Again freedom of choice is the goal.
Currently (180501) HealOps has been tested with:
Time-series backend
- OpenTSDB.
Metric visualization
- Grafana.