Pingdom is the most affordable one I've seen recently.  You can try it out
with one URL for free
https://www.pingdom.com/free

It also has some other nice free tools.
http://tools.pingdom.com/fpt/



--
Daren Darrow, dar...@gmail.com

On Thu, Aug 6, 2015 at 12:02 AM, Bryan Tong <cont...@nullivex.com> wrote:

> Hello,
>
> We have been using Zabbix with great success on 900 hosts. I would
> recommend it, however I must agree the learning curve can be pretty steep.
> I think of Zabbix more like a piece of networking equipment where it wont
> do anything until everything is configured correctly. It is far from plug
> and play, but very powerful and flexible.
>
> Thanks
>
> On Thu, Aug 6, 2015 at 12:59 AM, David Hofstee <da...@mailplus.nl> wrote:
>
> > We use Zabbix for local monitoring. Quite powerful (Nagios crapped out a
> > lot on larger setups, although 300 is not large). There is a learning
> curve
> > for Zabbix.
> >
> > We have a few VPS'es outside our network for DNS reasons. They are
> > configured as (pushing) monitoring nodes too. Bye,
> >
> >
> > David Hofstee
> >
> > Deliverability Management
> > MailPlus B.V. Netherlands (ESP)
> >
> > -----Oorspronkelijk bericht-----
> > Van: NANOG [mailto:nanog-boun...@nanog.org] Namens sathish kumar Ippani
> > Verzonden: Thursday, August 6, 2015 4:24 AM
> > Aan: nanog@nanog.org
> > Onderwerp: free Tools to monitor website performance
> >
> > Hi All,
> >
> > Thanks to all for reviewing my topic, may it is slightly off topic.
> >
> > We have almost 300 URL's (local and web) and we want to monitor few of
> > them which are very critical URL's for web access and local access.
> >
> > I would like to know is there any free tool or software with I can use to
> > monitor url performance in terms of response time. Which gives more
> > information like how much time it taken to connect the server and time to
> > load the page and total response time.
> >
> > Thanks in advance.
> >
> >
> >
> > --
> > With Regards,
> >
> > Sathish Ippani
> >
>
>
>
> --
> eSited LLC
> (701) 390-9638
>

Reply via email to