Hello Rodrigo,
please do not answer to me directly but to the mailing list, where
others who might have a similar question can benefit from your case.
As I understood your last mail, you do not have a performance issue at
all. It seems your question is why the check interval of your checks is
different between checks.
I can find nothing peculiar in the output you provided. From all I can
see the HTTP check and the PING check are deliberately configured for a
check interval of 5 minutes (HTTP) and 1 minute (PING).
If you want that to be different, you will have to change your
configuration, that is change the "check_interval"-value.
Regards
- Robert
On 06/25/2011 02:01 PM, rodrigo contreras wrote:
Dear Robert
Description: ICINGA 1.2.1
Services are monitored 10 servers and 60 computers
This is the print screen
Current Status:
WARNING
(for 127d 22h 4m 20s)
Status Information: HTTP WARNING: HTTP/1.1 401 Authorization Required
- 872 bytes in 0.001 second response time
Performance Data: time=0.000777s;;;0.000000 size=872B;;;0
Current Attempt: 4/4 (HARD state)
*Last Check Time:* *25-06-2011 07:51:02*
Check Type: ACTIVE
Check Latency / Duration: 0.161 / 0.007 seconds
*Next Scheduled Check: * *25-06-2011 07:56:02*
Last State Change: 17-02-2011 10:48:27
Last Notification: N/A (notification 0)
Is This Service Flapping?
NO
(0.00% state change)
In Scheduled Downtime?
NO
Last Update: 25-06-2011 07:52:42 ( 0d 0h 0m 5s ago)
Active Checks:
ENABLED
Passive Checks:
ENABLED
Obsessing:
ENABLED
Notifications:
DISABLED
Event Handler:
ENABLED
Flap Detection:
ENABLED
however, I realized that another service drop or rise times, in this
case this other service is a time of 1 minute.
Current Status:
OK
(for 2d 14h 28m 56s)
Status Information: PING OK - Packet loss = 0%, RTA = 0.46 ms
Performance Data: rta=0.462000ms;100.000000;500.000000;0.000000
pl=0%;20;60;0
Current Attempt: 1/3 (HARD state)
*Last Check Time:* *25-06-2011 07:53:34*
Check Type: ACTIVE
Check Latency / Duration: 0.306 / 4.012 seconds
*Next Scheduled Check: * *25-06-2011 07:54:34*
Last State Change: 22-06-2011 17:25:29
Last Notification: N/A (notification 0)
Is This Service Flapping?
NO
(0.00% state change)
In Scheduled Downtime?
NO
Last Update: 25-06-2011 07:54:22 ( 0d 0h 0m 3s ago)
Atte.
Rodrigo
Chile.
------------------------------------------------------------------------
From: [email protected]
To: [email protected]
Subject: RE: [icinga-users] Help me with ICINGA, Favor su apoyo con ICINGA
Date: Thu, 23 Jun 2011 06:10:14 -0400
Dear Robert
Thanks for your help.
In the first instance buscare details required for a better analysis
and better respond and discuss a possible solution to the delay times.
Note: Sorry for my English.
Greetings from Chile.
Atte.
Rodrigo Contreras.
------------------------------------------------------------------------
Date: Thu, 23 Jun 2011 04:04:55 +0200
From: [email protected]
To: [email protected]
Subject: Re: [icinga-users] Help me with ICINGA, Favor su apoyo con ICINGA
Hello there,
first of all I'd suggest that you write in English, so that everyone
can understand you.
As far as I understand your trouble, you do have a very large icinga
installation and the web frontend is too slow to use it properly.
Perhaps you could tell us further details about your setup. Icinga
version, number of checks per minute (overall sum of checks divided by
the average check period), basic hardware setup (RAM, CPU),
distribution (if you do use distributed monitoring) and the types of
checks you prominently use. Further information like average CPU and
memory usage and system load would be helpful, too, for a first overview.
If you measure frontend response time in minutes, you have a major
problem at hand.
A first, vague shot at what you can do now:
- set up a ramdisk and configure the objects.cache and status.dat
files, possibly even the check result spool directory into that
ramdisk (caution: do NOT place the retention.dat file in there)
- increase the check period of your checks
- evaluate whether you can use the option "enable large installation
tweaks". If possible, do so.
If that still does not help, set up the mklivestatus broker module and
try the web frontend "thruk".
You should do these steps in that order and take notes of how the
behaviour of the system changes with each step. Good luck.
Regards
- Robert
On 06/22/2011 10:25 PM, rodrigo contreras wrote:
Estimados Srs.
>
> En primera instancia les escribo para informar que ocupamos
ICINGA donde trabajamos y quisiera saber como puedo mejorar los
tiempos de refresco en pantalla Web de cada servicio que estan en
sus respectivos servidores.
> el tiempo de demora es de 6 a 10 minutos en refrescar la
pantalla Web.
> Favor su apoyo para reducir estos tiempos!!!
>
>
> Saludos.
>
> Rodrigo
> Chile.
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with vRanger.
Installation's a snap, and flexible recovery options mean your data is safe,
secure and there when you need it. Data protection magic?
Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________
icinga-users mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/icinga-users
------------------------------------------------------------------------------
Simplify data backup and recovery for your virtual environment with
vRanger. Installation's a snap, and flexible recovery options mean
your data is safe, secure and there when you need it. Data protection
magic? Nope - It's vRanger. Get your free trial download today.
http://p.sf.net/sfu/quest-sfdev2dev
_______________________________________________ icinga-users mailing
list [email protected]
https://lists.sourceforge.net/lists/listinfo/icinga-users
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/icinga-users
