<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> Indeed, that would be ok too, since then you can disable the host check and rely entirely on service checks so you get all the service checks. Almost as good. Of course it won't say host down, but it will say ping failed so you can tell from that. Another down side is that it will pollute your web interface with loads of trivial services, whereas it nice at the moment when all you see is the intended service. It would kind of spoil the web interface in my opinion. I think I will just wait for this to be done at the developer side, so that it is part of the normal configuration options. -h <pre class="moz-signature" cols="72">Hari Sekhon</pre> Morris, Patrick wrote: <blockquote cite="midCD18C81835E18A40A64C4A0D16A237BE05B31233@ATAEXC01.americas.cpqcorp.net" type="cite"> <blockquote type="cite"> <pre wrap="">well, think about it, if you have service down alerts you may think that the service is broken or crashed or switched off. If you see both service and host alerts then you know which services are broken and you can also immediately see that it is due to the machine being down, so you don't waste time trying to remotely connect to it. It's more informative. </pre> </blockquote> <pre wrap=""> There's nothing to stop you from having a service check, such as a ping check, that tells you whether the host is up or not. </pre> </blockquote> </body> </html>