|
| 1 | +# check_mk Plugin for Proxmox Backup Server |
| 2 | +[](https://github.com/inettgmbh/checkmk-proxmox_backup_server/actions/workflows/release.yml) |
| 3 | + |
| 4 | +This check_mk extension adds checks Proxmox Backup Server: |
| 5 | +* Datastore (Size, Usage) |
| 6 | +* Garbage collection |
| 7 | +* Verify jobs |
| 8 | + |
| 9 | +## Warning |
| 10 | +This extension is still work in progress and **produces a huge agent output** |
| 11 | + |
| 12 | +## Installation |
| 13 | +The mkp archive can be downloaded directly from the [release](https://github.com/inettgmbh/checkmk-proxmox_backup_server/releases/latest) and installed by following the [documentation of check_mk](https://docs.checkmk.com/latest/en/mkps.html). |
| 14 | + |
| 15 | +## Building |
| 16 | +Usually you don't see a section as how to build an mkp, because usually it's done like check_mk suggests using [WATO](https://docs.checkmk.com/latest/en/mkps.html#_creating_packages) or [CLI](https://docs.checkmk.com/latest/en/mkps.html#_creating_a_package). |
| 17 | +But we made it easier and included two helper tools into this repository, that depend on the tool [python-mkp](https://github.com/inettgmbh/python-mkp), which is a fork of [tom-mi/python-mkp](https://github.com/tom-mi/python-mkp). |
| 18 | +Unfortunally, the original tool, which can be installed using `pip` **cannot** be used because it wouldn't package some files. |
| 19 | + |
| 20 | +### Requirements |
| 21 | +* python-mkp |
| 22 | + |
| 23 | +just run |
| 24 | + |
| 25 | +```sh |
| 26 | +$ build/mkp-pack |
| 27 | +``` |
| 28 | + |
| 29 | +## Contributing |
| 30 | + |
| 31 | +### issues, you can't fix / ideas, you can't implement |
| 32 | + |
| 33 | +Use GitHub's [Issues](https://github.com/inettgmbh/checkmk-proxmox_backup_server/issues): |
| 34 | +Try to explain as clear and short as possible. |
| 35 | + |
| 36 | +### you want to write some code? |
| 37 | + |
| 38 | +* Use Pull requests |
| 39 | +* Sign off your commits |
| 40 | +* Adapt to the coding style. Divert from it, if doing so increases readability. |
| 41 | +* Don't check in IDE specific files or products of a build. |
| 42 | + |
| 43 | +## Issues |
| 44 | +yes, we have those |
| 45 | +This extension 'works for us' right now, but it's far from optimal. |
| 46 | + |
| 47 | +* Agent output is way to much and must be optimized |
| 48 | +* Names of metrics should be changed |
| 49 | + |
| 50 | +## TODOs |
| 51 | +(even more, than issues) |
| 52 | + |
| 53 | +* Check of sync jobs |
| 54 | +* Check prune jobs |
| 55 | +* Check tape jobs |
| 56 | +* Check, if verify jobs are running |
| 57 | +* Optimize parsing of agent output |
| 58 | +* Add check parameters for timeouts of verify, garbage collection and prune jobs |
| 59 | +* Move todos and issues to GitHub issues and projects (without being recursive) |
| 60 | + |
0 commit comments