Go to All Forums

Bob - difference between Server Monitor and On Premise Poller


Hi all

Can any budy define what is the main difference between Server Monitor and On Premise Poller..

Regards
Like (0) Reply
Replies (4)

Hi Bob,

Thanks for raising your query here.

Site24x7's Server Monitoring feature is an agent based monitoring which  will monitor the CPU, memory, disk and network utilization of your Windows and Linux servers. On the other hand, On-Premise Poller is primarily an installable agent required for  monitoring resources on the intranet. 

Say for example, you would want to monitor the uptime and performance of a Windows server at your end. You can go ahead and monitor the same by installing a Windows agent in the server. This will also fetch the availability and performance of other services and processes running on that server. 

Incase you wish to monitor an intranet URL(say the employee portal in your organization), you can install the On-Premise Poller agent in one of the machines in the local network and monitor the intranet URL.

Here are some screenshots of the metrics captured in both the features.


Windows Server Monitor





On-Premise Poller Screenshot



Regards,
Sushma.

Like (0) Reply

On-premise poller in short, it can help you monitor resources behind the firewall. 
Quick snapshot - how it works



Like (0) Reply


Ok thanks for your reply... does the On Premise Poller shows the availability of server also or not ?
Like (0) Reply

The On-Premise Poller can tell whether the server is up or down by doing a ping test. The On Premise Poller has the following capabilities in it : ping, URL, port, SSL etc.

One important deployment architecture difference between On-Premise Poller and Server Monitoring agent is the On-Premise Poller is agentless. You install the Poller only once on a server in the network and all monitoring will take place from this specific installation.

If only uptime is what you want, then the poller is a good bet to monitor servers. However to get server monitoring coverage, use the agent based "Server Monitoring".
Like (0) Reply

Was this post helpful?