The Chum OBS project is here for main and here for testing. Packages: Best installed through Chum GUI.It’s in alpha stage at the moment, but you can find it here, and it will be released to chum “when it’s ready”. I have also started to work on a GUI app. Look at monit -help and devel-su monit status for some output.įor your convenience, a bash-completion file is available at /etc/bash_completion.d/monit When you call monit on the command line it acts as an interface to a running deamon. The daemon has a web interface at so you can monitor your monitoring and interact with the different monitoring targets. Note there is a startup delay configured, you will have to wait for some minutes until the interface comes up. (You can also let monit run as a regular user, but you’ll have to set that up yourself using the official docs, and creating a config at ~/.monitrc.) Start/Stop the daemon using systemctl rvice. Upgrading from previous M/Monit releases (2.3 or later) The upgrade program can be used to automatically copy database and configuration files from the previous installation and update the database schema. Of course you can also publish RPM files to place files in there (or use Patchmanager, although that’s kind of abusing it). So if you decide to play around with monit, and write some useful configurations, please submit them at GitHub - nephros/monit: monit and I will include them in the next iteration of the -contrib package. ![]() The monit-contrib is intended to be expanded by YOU, the hackers, devs and power users with your configurations and additions. To enable any of the shipped configuration snippets, make a symlink from /etc/monit.d/available/foo.conf to /etc/monit.d/foo.conf. This package will create dirs at /etc/monit.d/available and /etc/monit.d/scripts. There is also an extra package called monit-contrib, which ships a couple of example config snippets you can try out. Please use that directory to place your custom configurations. Any file ending in *.conf will be picked up by the monitoring daemon. The package comes with a configuration structure at /etc/monit.d/. It is more about reporting and reacting to changes in the system state, send alerts, execute scripts on failure and so on. See Monit Presentation for an introduction, and M/Monit | Wiki for details on what it can do.Ĭontrary to most tools in the class monitoring its purpose is not so much drawing pretty graphs of historical data. You can use it to monitor certain properties of your system, remote systems, programs, processes and much more. ![]() I have packaged and pushed to Chum Monit, a system monitoring and configuration tool.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |