I have been using Kaseya for over six months now, and even after the recent update to version 5.0, the network monitoring functionality remains pretty much a joke. I don’t understand how this app became so popular in the MSP world. Here’s a list of reasons why:
- No concept of “state” for services - Kaseya keeps track of host state (ie: online/offline) with a nice little icon, but it does not do anything similar for services. Therefore, there is no way to get a complete picture of a network’s current state “at a glance.” Services should not be treated like 2nd class citizens this way, because plenty of services are just as critical as (if not more than) the actual hosts they are running on.
- No alerts when a service returns to an “OK” state - It’s not enough to receive an alert just when a host/service check fails. You need a corresponding alert when it starts succeeding again too, and here’s why: False alarms are pretty much a fact of life with all monitoring applications. There are lots of reasons why a check might fail every now and then (network congestion, etc.). Therefore, I don’t want to have to scramble every time I see an alert just to find out that the service is already back up again. I want the monitoring application to tell me when it’s back up. This is especially important when I don’t have immediate access to a computer (e.g. if I’m on the road and I have alerts going to my phone).
- Graphs are limited to ~2000 data points - This is the problem with storing raw performance data in a SQL database (I admit that I am simply assuming that’s what they have done here). More data makes a slower database, so it makes sense that they would hard-code a limit on the amount of data that can be stored. But how in the hell do they expect their customers to do trend analysis with only ~2000 data points? Assuming a service check every 10 minutes: 60 minutes * 24 hours / 10 = 144 data points per day. ~2000 data points total / 144 per day = a history of ~14 days. Compare this to something like Cacti which can easily handle years worth of performance data using RRDtool.
- SNMP monitoring will bring your network to its knees - Amazingly, there is no way to modify the polling interval for SNMP queries. It appears that the Kaseya agent will simply execute snmpget in rapid succession until you notice that your server’s CPU is pinned to 100% and you are forced to disable SNMP monitoring altogether. Even if they increased the hard-coded polling interval, you still have no control over the size of your graphs due to the data point limit listed above (in my experience, you might get 1-2 days if you’re lucky). What baffles me the most is that you can set the polling interval for WMI monitoring. So why would they not implement this for SNMP too? I don’t get it.
To be fair, Kaseya seems to be paying a lot of attention the user complaints on their forums lately, and they’ve already started to address some of these problems. Hopefully I’ll have less to complain about in the coming weeks.
6 Comments
Their remote assistance is a joke too. It works fine if you’re trying to remote to a machine that has the agent already installed, but if it doesn’t you will be explaining to the user how to install an ActiveX control. Good luck with that. Also installing the activeX control will not work unless the user is a local administrator… I ran into someone who wasn’t and they needed my help. I wasn’t able to help them thanks to Kaysea.
Why not just do what everyone else does and have the user download an executable? Because the programmers are half-wits who have never tried to remotely assist a user using their own code. Who the hell uses activeX anymore? Use GoToAssist or PCHelpware instead, they know what they’re doing when it comes to remote assistance. If you’re going to implement a feature in your product do it right or don’t do it at all.
Shows that there are myths. Remote Control utilizes 5 different methods and activex is not necessary. A url link can be clicked to direct download a dll that initiates the connection.
On monitoring, they are great. They listen and have opened up monitoring to unlimited events and alarms. If you are a shoddy msp you will flood the system with millions of events in minutes but as I understand it they are going to add some protections for those situations. They do listen.
anon: dont tell me “they are great” on monitoring until you address at least one of the issues i’ve listed above. otherwise, you make yourself sound like a very uninformed person (which i am assuming is why you posted anonymously in the first place).
if anyone has actual solutions for me, i’m all ears. im not here to bash kaseya for the hell of it. i have work to do, and i would honestly love to know how other msps have been dealing with these issues.
You are right that in the latest version of Kaseya ActiveX is not required anymore and the user can download and run an executable. My mistake. However remote assistance is still garbage because the remote user needs local administrator rights to run. Instead of fixing this, the Kaseya programmers put this in the web interface:
“Attention standard users! Administrator privileges are required to request remote assistance.
On Vista, right mouse click on Internet Explorer and start it by choosing the menu selection Run As Administrator.
On all other systems, be sure you are logged in as a user with administrator privileges.”
I read this as “We are too lazy to fix our broken code. Kaseya remote assistance will not work in all cases, so keep your fingers crossed.” How hard is it to fix this? Not very:
The RealVNC server program (winvnc4.exe) that is included in the Kaseya remote assistance agent listens on port 5900. This can run as a limited user. RealVNC picks up its settings from HKEY_LOCAL_MACHINE/SOFTWARE/RealVNC/WinVNC4, but it also accepts a wealth of command-line options (try winvnc4.exe -h). So it is as simple as changing your script/code that starts winvnc.exe, but it is easier to write a warning that says “administrator privileges are required”.
Hi Guys,
I’m trying the Kaseya Product at the moment, we are a solution provider to small companies and I’m looking for a product to meet their needs. I have looked at other products such as level platforms, heroix etc. From a budgetary and business models the kaseya appears to resemble closet what Im looking for.
Technically though I have to ensure it will do what it’s supposed to. I dont want my techs flooded with useless information which eventually they will ignore .. and then miss something crucial.
I do agree with SNMP being issues and also the Remote control is pretty poor.. it’s much too slow. But to be fair most of these products don’t seem to be built for MSP’s.. to date kaseya seems the closest I’ve found.
As i’m just demoing the product at the moment I’m trying to get some overall research to see how others find it in production but I’m having some difficulty getting info.
Any pointers/comments would be great.
Not to add to the Kaseya bash fest, but be careful. their support is the worst of any of the companies we deal with including HP which is really saying something. Weeks can go by before a ticket is responded to, you can sit on hold for support for several hours with no status updates or anything. When they do respond to online support they provide a terse answer that does not address the problem and then close the ticket. The only way we get any sort of response is to raise our support request through our sales person who sends it to the director. As an MSP if we treated our customers that way we would no longer be in business. Until they fix their support I would not recommend purchasing their product.