Kaseya Community

Linux agent 6.2 installed, what sort of monitoring can i do?

  • Hi guys i have the agent installed redhat5 and 6 linux ... but as far as i can see, there isnt much i can do.

    I would like to monitor this servers, they are basic LAMP stack.


    Any ideas?





  • [edited by: Josh Tipping at 9:04 PM (GMT -7) on 10-11-2011] browser bug
  • Sorry, my post clearly didn't work! With linux, agent procedures can give you the ability to do an awful lot, considering the power of Bash/grep/awk etc.

    For example, the following bash script could be written to a machine, executed, and the output logged back into a script for checking with an IF step, all with a nice easy procedure, to monitor the Apache process. This is just an idea, you could use a similar process to monitor a number of different things.


    run=`ps ax | grep /usr/sbin/httpd | grep -v grep | cut -c1-5 | paste -s -`

    if [ "$run" ];


    echo “Apache is running”


    /etc/init.d/httpd start


    Hope this helps a little.

  • Wow, nice tip josh... I better read up on my linux scripting, and try a few scripts.  is there any documentation out there that i can use, to guide me ... like a kaseya how to?

    thank you very much

  • To the best of my knowledge, there is no documentation written specifically towards agent procedures written for Linux.

    scripts like the tend to work well (although "/etc/init.d/httpd status" might be simpler than Josh' ps line).

    One thing to remember with scripts running services from /etc/init.d, is that they tend to behave differently on different

    Linux distributions (ie, RedHat Enterprise vs Ubuntu).

    On another note, the monitoring code for the Linux agent has been written and is currently being tested. Unless something

    unforeseen happens, it should be available in the next release.

    Gordon - Linux Agent Development Team

  • When will the next release be?  Need beta testers?  :-)

  • Bill, being a developer I'm not familiar with what has been publicly announced and what is currently proprietary information. You would be better served asking these questions from someone on the sales side of things. Not only do they have a better idea of when the next release is expected, but they'll have a better idea of what to do to become a beta tester.

    I will talk to our CTO and see if he has any suggestions for getting you a beta version. However, I'm not likely to be the person making this decision. The best I can do is forward you're request to the right people (assuming I can find out who they are:-), and to let them make their decisions.