Como eu posso automatizar para que um check não alarme num determinado perído
de tempo.
EX: Por exemplo ao rodar uma rotina, tenho um check que fica alarmando até que
esse seja finalizado.
--
Download Intel#174;
Olá PessoALL,
Estou com um problema:
Tenho um determinado host (servidor windows) no qual faço checagem de alguns
serviços, tipo: tráfego de rede, espaço em disco, serviço SQL, etc.
Mas quando o servidor cai, todos os serviços alarmam no Nagios também (o que é
lógico, pois o servidor saiu do
Crie periodos.
No arquivo timeperiods.cfg vc cria e depois coloca no host a opcao
check_period nome do periodo criado
Ex:
define timeperiod{
timeperiod_name seg-sex_07-16
alias seg-sex_07-16
monday 07:00-16:00
tuesday 07:00-16:00
LinkedIn
I'd like to add you to my professional network on LinkedIn.
- Marco Antonio
Confirm that you know Marco Antonio Tirado Godoy
https://www.linkedin.com/e/isd/1102226143/z52XZRMp/EML-invg_56/
--
(c) 2010, LinkedIn
Am 24.02.2010 15:03, schrieb Trond Hasle Amundsen:
Nicole Hähnelm...@nicole-haehnel.de writes:
Hi
I get this message on one pe830 (OM 6.1.0) :
CRITICAL: [ xxx] Physical Disk 0:0 [Wdc WD1600JS-55MHB0, 160GB] on ctrl 0
needs
attention:
-- SYSTEM: PowerEdge 830, SN: xxx
INTERNAL
Nicole Hähnel m...@nicole-haehnel.de writes:
it's a windows server.
So I'm using check_openmanage with snmp.
check_openmanage -s -C $ARG1$ -H $HOSTADDRESS$ -e -i -p --state --check
intrusion=1,alertlog=1,esmlog=1 -o 3 --htmlinfo de
List of Physical Disks on Controller CERC SATA 1.5/6ch
Am 25.02.2010 15:38, schrieb Trond Hasle Amundsen:
Nicole Hähnelm...@nicole-haehnel.de writes:
it's a windows server.
So I'm using check_openmanage with snmp.
check_openmanage -s -C $ARG1$ -H $HOSTADDRESS$ -e -i -p --state --check
intrusion=1,alertlog=1,esmlog=1 -o 3 --htmlinfo de
List
Nicole Hähnel m...@nicole-haehnel.de writes:
I tested the new version:
CRITICAL: [xxx] Physical Disk 0:0 [Wdc WD1600JS-55MHB0, 160GB] on ctrl 0 needs
attention:
-- SYSTEM: PowerEdge 830, SN: xxx
INTERNAL ERROR: Use of uninitialized value in string eq at /usr/lib64/nagios/
FYI, The reason this wasn't working was that there was 'use' directive in the
service template that was using a template that also has a servicegroups
directive for another service group (that line got edited out of my example).
Putting a + sign in front of the ebusiness servicegroup name did
Am 25.02.2010 16:42, schrieb Trond Hasle Amundsen:
Nicole Hähnelm...@nicole-haehnel.de writes:
I tested the new version:
CRITICAL: [xxx] Physical Disk 0:0 [Wdc WD1600JS-55MHB0, 160GB] on ctrl 0
needs
attention:
-- SYSTEM: PowerEdge 830, SN: xxx
INTERNAL ERROR: Use of
Hello,
I have a strange issue with nrpe
- nrpe compiled with support for arguments
- option dont_blame_nrpe = 1
plugins fail if I pass arguments; tested with check_tcp, check_icmp and
check_load; none of them works if arguments come from the nagios
station; they all work if arguments are
On Feb 25, 2010, at 1:56 PM, Joao Ferreira gmail wrote:
bellow a log with details; the only difference between the 1st and the
second is that the 2nd receives args from the client nagios station
Feb 25 15:17:55 ebox nrpe[10779]: Running
command: /usr/lib/nagios/libexec/check_tcp -H
Are you sure your configs are correct? I noticed your config seems to
specify two differnet locations for the check_tcp plugin:
Feb 25 15:17:55 ebox nrpe[10779]: Running
command: /usr/lib/nagios/libexec/check_tcp -H localhost -p 22
Feb 25 15:18:49 ebox nrpe[10827]: Running
command:
Hi,
Any recommended method to monitor customized init scripts. I know
check_tcp will only monitor ports.
Please suggest.
Thanks,
Kaushal
--
Download Intel#174; Parallel Studio Eval
Try the new software tools for
14 matches
Mail list logo
