sorry, I forgot to change the title of the message

regards

Dear Jean,

How is this related to the Checkpoint alert creation problem?

More no topic, a lot of information is missing to correctly diagnose the issue, but in any case, the alerting matching is very generic and definitely should not be buggy for only a checkpoint fanspeed sensor...

Tom

Hi,

 

What is the process to integrate the MIBs manufacturer Huawei in Observium?

Thank you for your help

 

Regards

 

Jean Caruso

 

De : observium [mailto:observium-bounces@observium.org] De la part de Moerman, Maarten
Envoyé : mercredi 2 novembre 2016 13:48
À : Observium Network Observation System <observium@observium.org>
Objet : Re: [Observium] CheckPoint alert creation problem

 

You should give some developer access to a checkpoint to verify if this is the case then.

 

Maarten

 

From: observium <observium-bounces@observium.org> on behalf of Laszlo Nemeth <laszlo.nemeth@emarsys.com>
Reply-To: Observium Network Observation System <observium@observium.org>
Date: Wednesday, November 2, 2016 at 11:17 AM
To: Observium Network Observation System <observium@observium.org>
Subject: Re: [Observium] CheckPoint alert creation problem

 

I made a little debug.

 

So the alert:

 

Device: hostname match *fw*

Entity type: Sensor

Entity match: sensor_class equals fanspeed

Test condition: sensor_value greater 3000

 

Result: no any device match

 

If I replace the hostname with “hostname match * “ it match with 4 device’s 38 “fanspeed” sensor. But this devices are Cisco routers (ASR) and PC Linux servers. No any firewall that have fanspeed sensor (more than 10 devices there I see the Fanspeed RRD graphs under these devices HEALTH menu) ).

 

So looks like if the device not ASR or PC (yes I know it is may be not correct, but from my point of view this is the situation) the Observium (8039) not recognize the fanspeed sensors as fanspeed sensor.

 

Laszlo

 

From: observium <observium-bounces@observium.org> on behalf of Laszlo Nemeth <laszlo.nemeth@emarsys.com>
Reply-To: Observium Network Observation System <observium@observium.org>
Date: 2016. November 2., Wednesday 9:33
To: Observium Network Observation System <observium@observium.org>
Subject: Re: [Observium] CheckPoint alert creation problem

 

Ez a feladó nem felelt meg a csalást ellenőrző vizsgálatunkon, és lehet, hogy nem az, akinek tűnik. Információ az identitáshamisításról

Visszajelzés

Hi

 

Yes, I set it to Sensor type. But it looks like the check not match with any device. I have more than 50 check, this is the only that not match with any device’s sensor.

 

Laszlo

 

From: observium <observium-bounces@observium.org> on behalf of "Moerman, Maarten" <mmoerman@ebay.com>
Reply-To: Observium Network Observation System <observium@observium.org>
Date: 2016. October 28., Friday 16:23
To: Observium Network Observation System <observium@observium.org>
Subject: Re: [Observium] CheckPoint alert creation problem

 

Have you selected the right entity type when adding an alert-checker? It needs to be of type “sensor” , it doesn’t work when you leave it on “device”

 

Maarten

 

From: observium <observium-bounces@observium.org> on behalf of Laszlo Nemeth <laszlo.nemeth@emarsys.com>
Reply-To: Observium Network Observation System <observium@observium.org>
Date: Friday, October 28, 2016 at 3:37 PM
To: Observium Network Observation System <observium@observium.org>
Subject: [Observium] CheckPoint alert creation problem

 

Hello,

 

I have a CheckPoint 2205 device. It is supported by Observium, so we love it :D

 

I would like to create an alert for it’s fan speed.

 

I do a normal alert like our other looks like:

 

Device: hostname match *cpfw01*

Entity match: sensor_class equals fanspeed

Test condition: sensor_value greater 3000

 

With this settings if i push a Rebuild, it shows 0 entities.

 

How can i check what is wrong? I tried to change the fanspeed to temperature, but the problem is similar, 0 entities after rebuild.

 

I attached a picture about the graphs of the device.

 

Hmm... if i run a „rebuild” there are see lot of devices but there is no any „FW” devices however we have more whit this FW prefix. May be this is the problem? It looks like this list doesn’t show all of our devices.

 

Thanks

 

Br

Laszlo

 

Ce message peut contenir des informations confidentielles, couvertes par le secret professionnel ou réservées exclusivement à leur destinataire. Toute lecture, utilisation, diffusion ou divulgation sans autorisation expresse est rigoureusement interdite. Si vous n'en êtes pas le destinataire, merci de prendre contact avec l'expéditeur et de détruire ce message.
This email may contain material that is confidential, privileged and/or attorney work product for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

Ce message peut contenir des informations confidentielles, couvertes par le secret professionnel ou réservées exclusivement à leur destinataire. Toute lecture, utilisation, diffusion ou divulgation sans autorisation expresse est rigoureusement interdite. Si vous n'en êtes pas le destinataire, merci de prendre contact avec l'expéditeur et de détruire ce message.
This email may contain material that is confidential, privileged and/or attorney work product for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

_______________________________________________

observium mailing list

observium@observium.org

http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

Ce message peut contenir des informations confidentielles, couvertes par le secret professionnel ou réservées exclusivement à leur destinataire. Toute lecture, utilisation, diffusion ou divulgation sans autorisation expresse est rigoureusement interdite. Si vous n'en êtes pas le destinataire, merci de prendre contact avec l'expéditeur et de détruire ce message.
This email may contain material that is confidential, privileged and/or attorney work product for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.