topic Re: Syslog Component in Components

Syslog Component

Christian_L — Thu, 17 Jul 2008 20:29:27 GMT

Please post your questions or feedback on the Syslog Component here.

(This component will be posted within a week of the start of this thread. Until then the link above will return an error.)

Re: Syslog Component

Joe_H1 — Fri, 29 Oct 2010 16:52:35 GMT

Any chance your group has already developed a new reference library for RFC 5424 that obsoleted RFC 3164:

http://en.wikipedia.org/wiki/Syslog

One thing I like about the new standard is fractional second resolution on the timestamp, where 3164 only has whole seconds.

Thanks for all your help.

Re: Syslog Component

xgatc — Tue, 07 Jun 2011 21:16:07 GMT

Hello

I have used syslog in LV for Windows in applications. I wonder if there is a syslog in LV for Linux. I would like to use syslog collector on Linux machine for our third party partner.

any suggstion is more than welcome.

cheers

Re: Syslog Component

Christian_L — Wed, 08 Jun 2011 15:57:39 GMT

xg,

The LabVIEW Syslog client and collector is written completely in LabVIEW source code, so it can be run on any LabVIEW platform supporting UDP including Linux. You can copy the source files from your Windows system to Linux and they should work.

I have added two more downloads to the Developer Zone document which are a VI Package (*.vip) for use with VI Package Manager and a ZIP file containing the source files. Either one of these can be used to place the files directly on a Linux machine.

Re: Syslog Component

xgatc — Wed, 08 Jun 2011 16:57:19 GMT

Hi, Christian

Many thanks. is this document ni.com/devzone/cda/epd/p/id/5980 ?

I will have a go for that

cheers

Re: Syslog Component

xgatc — Thu, 09 Jun 2011 10:54:50 GMT

Hello, Christian

I downloaded the syslog1206_source.zip, unzip and placed syslog directory under my LabVIEW 8.6/user.lib.

when I first tested the collector.vi example, it did not work. it turned out that the default port number of 514 is not working under Linux.

after I changed the default port to 6160 and also modified syslog_device.vi to have syslog port as 6160 and 6161, both collector.vi and device.vi examples work.

I now can start the collector.vi on Linux machine and run device.vi both on the Linux machine and on my windowXp Laptop.

again, many thanks

Re: Syslog Component

xgatc — Wed, 13 Jul 2011 09:13:54 GMT

Hello, Christian

I have an issue in using the Syslog Client application and wonder if you can suggest a way out.

I have two different applications ( LabView EXE) running on the same machine which like to send log message to the SyslogCollector ( running on another machine). The current syslog.device.init will only work for whichever the first running appllication, it fails if the second application tries to call it.

is there a way to deal with this situation? or we can not run more than one appliaction on the same machine for sysLog Device.

thanks

xiaofeng

Re: Syslog Component

Christian_L — Wed, 13 Jul 2011 15:05:28 GMT

xiaofeng,

This will require using two different UDP port numbers on your local comuter, one for each LV EXE. Currently the Syslog API does not support setting the local UDP port number.

Until we have the chance to add this feature you can add it yourself by modifying the Syslog Devioce Init.vi and syslog_Device Function Engine.vi (Init case).

In this case there is a constant labeled 'regular syslog port'. You will want to convert this to a control and export it out through the VI terminal connector to the top level API where you can set it differently in each of your applications.

Re: Syslog Component

xgatc — Thu, 14 Jul 2011 09:01:08 GMT

many thanks, Christian, I will have a go

xiaofeng

Re: Syslog Component

clendon.gibson@canrig.com — Wed, 21 Aug 2013 16:53:32 GMT

The VI "Syslog Device Send.vi" has an error cluster based case structure. If an error is present, nothing is done.

If there is no error and the "Message Tag" and "Message Content" string controls are empty, then it tries to read the error cluster to create the syslog message.

The upshot is that errors reported in the error cluster will cause the syslog message to not be sent, even if the intent is to send the error message in the error cluster.

Re: Syslog Component

Christian_L — Thu, 22 Aug 2013 14:48:02 GMT

Clendon,

You are absolutely correct. It looks like the error case structure was added in a recent version of the component in an effort of adding error handling to all VIs. I will remove it and repost the VI package.

Re: Syslog Component

LeifS — Wed, 23 Apr 2014 20:44:00 GMT

Hi,

I think I've found a bug in the SubVI "syslog_Hostname.vi"

The boolean constant value makes the VI to return the first byte of the IP address instead of the hostname.

Change the value to FALSE as below instead gives the hostname in return:

Re: Syslog Component

Christian_L — Fri, 25 Apr 2014 19:44:57 GMT

Leif,

Thank you for the error report. Attached is an updated VIP, which should be posted to the LV Tools Network VIPM repository in a few days.

Re: Syslog Component

LeifS — Sun, 15 May 2016 17:43:49 GMT

Hi again,

We have noticed that the send function (Syslog Device Send.vi) executes quite slow in some environments. After some performance analyzing we found that the blame goes to syslog_Hostname.vi , which executes the StringToIP and IPToString for each time a Syslog message is sent.

This is easily fixed by caching the hostname in the VI like this:

It would be nice if you could release a new version with this improvement.

Kind regards

LeifS

Re: Syslog Component

Christian_L — Wed, 18 May 2016 15:56:49 GMT

Thank you LeifS,

I have added your suggestion and built a new package. This will be added to the LabVIEW Tools Network repository soon.

Re: Syslog Component

LeifS — Thu, 25 Aug 2016 09:44:26 GMT

Hi,

I also have run into this issue with the local IP port conflict, and although I certainly can fix it myself, I'd prefer NI to fix it and distribute a new version of the package.

Can you please do that?

Best regards

Leif Suonvieri

Midroc Automation, Sweden

Re: Syslog Component

Christian_L — Thu, 25 Aug 2016 19:33:53 GMT

I added the ability to specify the Client Port on the Init VI and rebuilt the package. (attached)

It has been added to the VIPM repository.

Re: Syslog Component

LeifS — Tue, 20 Sep 2016 11:51:30 GMT

Hi Christian,

Your latest fix was good, but only works if I have the Collector running on the same computer.

Could you please change so that I can select ClientPort agains a remote Syslog server?

Below I'm proposing a solution for this.

Best regards

Leif S

Re: Syslog Component

Christian_L — Tue, 20 Sep 2016 15:14:34 GMT

Thank you for the suggestion. I've attached the updated VIP.

Re: Syslog Component

RichardS_Dynex — Tue, 13 Mar 2018 14:27:12 GMT

Hi Christian,

RFC 3164 specifies that the total length of the syslog message including PRI and HEADER must not exceed 1024 bytes, but I can't see any such limit imposed in the component (so arbitrarily long content strings will be sent without truncation).

Should the message 'syslog_Device Function Engine.vi' truncate the message length to 1024 bytes?

Richard.