I got this working, so thank you!

If you ever release a new version, can you include the option for a third nagios host?

Thank you

es ist ein Bug im Connector. Im Quellcode steht in der Klasse Processor folgendes:

case “contains”: return value.Contains(compare);
case “containsIgnoreCase”: return value.ToLower().Contains(compare.ToLower());
case “equals”: return value.Equals(input.Value);
case “equalsIgnoreCase”: return value.ToLower().Equals(input.Value.ToLower());

Es muss aber bei Equals auch die Variable Compare anstatt input.Value stehen, da sonst das falsche XML Element genommen wird. Ich schau mal, ob ich im Laufe der Woche eine korrigierte Version hochladen kann… Wenn es dringender ist, einfach den Quellcode selbst korrigieren und im Visual Studio kompilieren (Quellcode ist ja immer im ZIP File enthalten).

Grüße

Markus

zunächst einmal ein großes Danke für diesen Connector, er hat mir jede Menge Arbeit erspart

Allerdings habe ich momentan ein Problem mit der processing.xml – um genauer zu sein mit dem Vergleichsoperand “equal”, den ich gern nutzen würde um die Resolutionstates zu verarbeiten.
-> Leider passiert an dieser Stelle nichts, die Regeln sind nach diesem Muster erstellt:

0
New Alert

Dennoch wird die Regeln einfach übergangen… verwende ich statt “equals” den Operand “contains”, wird die Regel angewandt.
Ich vermute das Problem beim “equals”, denn wenn ich mir den “$state” ausgeben lasse, sehe ich, dass dort wie erwartet die “0″ rauskommt.

Gibt es hier einen Bedienfehler auf meiner Seite, oder handelt es sich hier um einen Bug?

2. Currently I cannot understand your second question. Can you be more detailed or send me your config by e-mail (see Impressium)

with best regards

Markus

Got some questions and a small problem. The connector service won’t start automaticly when a reboot is done.

And I really would like to send notification subscriptions (because I only want to send specific monitors and rules) to the internal connector. Is that a possibility?

With kind regards, Sandra

I’ve been looking at this tool for a long time now and never needed to use it. Until recently, but there are some “small” bugs. It took me over a week to figure them all out.

1. in the manual there is no mentioning to move the processing.xml and where to find the log file (in my case ProgramData\kit)
2. the send_nsca.config file has the wrong extention in the zip file

yes you have to configure NCSA on your nagios server (the target with the ip 10.1.2.234). It is descripted in this article and the linked pdf: http://community.nagios.org/2009/06/11/nagios-setting-up-the-nsca-addon-for-passive-checks/.
After that you have to define a host with the name vrt-server-test.scom.be and with a passive check named p_scom.

I hoped it was helpful…

Markus

We succussfully installed the nagiostoscom connector in windows server 2003.
The log file is showing the following
***********************************************************************
5-4-2011 16:38:09: Send to Nagios C:\scom2nagios\send_nsca.exe commandline: -H 10.1.2.234 -d ; -c “C:\scom2nagios\send_nsca.cfg” -p 5667, Message: vrt-server-test.scom.be;p_scom;2;OleDB: Results Error

5-4-2011 16:38:10: Event send to nagios
***********************************************************************

In wireshark in ubuntu we can see that nsca packets were sent but how can see the messages in Nagios? How do you have to configure Nagios to receive these messages? Do I have to install nsca or something?

Thanks for help

Jonas

I can see that the source is included. Sorry for asking about that.

I ran send_nsca from the command line with the exact same flags and message as indicated in the log, and discovered the source of the problem. The connector is trying to read the send_nsca configuration file as “send_nsca.config” but the file provided with the application is named “send_nsca.cfg”. I renamed the file and the connector is successfully sending alerts to the nsca server now. Now I just have to configure Nagios…

Also, is the source code for the connector available?