rsyslog

High-performance log ingestion and ETL engine

rsyslog

High-performance log ingestion and ETL engine

How to setup RSyslog Windows Agent to monitor NetApp devices using backup *.evt files

Adiscon SupportUncategorized,

This article describes how to use RSyslog Windows Agent to monitor NetApp devices using the backup .evt files. In this guide we describe how to setup the service. For creating the actions, please refer to the our other guides.

There are basically two methods to monitor logs of NetApp devices. The first, described here, is to monitor the .evt files that the NetApp device generates. The second method is to monitor the device via the Eventlog API. Instructions can be found here.

The NetApp device basically offers to access the .evt files via a network share. Thus the files are easily accessible through our products.

Basically, we need to create the Event Log Monitor service in RSyslog Windows Agent. Simply right-click on services and from the popup list, choose “Add Service” and the “Event Log Monitor”.

Now disable all the currently available logs except for one. Double click on the one that is still checked. A new window opens.

In this new windows, enable the option “Read Eventlog from File”. The parameters belonging to this option are now available. Insert the file and path name into the field. Alternatively, you can use the browse button to navigate to the remote location of the NetApp and choose the file like that. You could now also change the “Type of Eventlog” if necessary.

Please note, that this method is also fit to monitor multiple files. You only need to change the file name accordingly and insert wildcards to replace name values like dates. This is good for cases, when a new log file is created every day and the filename reflects the date when the file was created, like below for file like adtlog.20130206110000.evt or adtlog.20130206121314.evt.

So thats it basically. You can now choose to forward the log messages via syslog to a central log host, write them into a database or use one of the many other options that are available in RSyslog Windows Agent.

How to setup RSyslog Windows Agent to monitor NetApp devices using Eventlog API

Adiscon SupportGuides for Windows Agent, ,

This article describes how to use RSyslog Windows Agent to monitor NetApp devices using the Eventlog API. In this guide we describe how to setup the service. For creating the actions, please refer to the our other guides.

There are basically two methods to monitor logs of NetApp devices. The first, described here, is to monitor the device via the Eventlog API. The second method is to monitor the device via the .evt files the device generates. Instructions can be found here.

The NetApp device basically offers to access the log storage via the Eventlog API. That makes it very easy to use our products to monitor NetApp devices.

Basically, we need to create the Event Log Monitor service in RSyslog Windows Agent. Simply right-click on services and from the popup list, choose “Add Service” and the “Event Log Monitor”.

In the next step, enable “remote EventLog monitoring”. Insert the hostname or IP of the NetApp device into the field. Verify the connection with the “Verify” button. You might need to run the MonitorWare Agent service with a account, that has both local administrative rights as well as rights to read the Eventlog of the NetApp device.

Now disable all the currently available logs except for Application, Security and System. Double click on the one that is still checked. A new window opens.

In this new windows, enable the option “Use Checksum to verify the last processed event”. The parameters belonging to this option are now available. Also enable “Always search for the last processed Event using the Checksum”. If these options are not enabled, polling the log messages will not work properly, because the NetApp logging system does not use a record number to identify single log messages. Repeat this step for the remaining two log types.

So thats it basically. You can now choose to forward the log messages via syslog to a central log host, write them into a database or use one of the many other options that are available in RSyslog Windows Agent.

librelp 1.0.7 released

Rainer GerhardsUncategorized

librelp 1.0.7 [download]: removed relpCltConnect2() API which was against librelp API philosophy. This was only introduced in 1.0.6 and been in the code for a very short time. So we decided that the best thing to do is actually remove it (there is NO known released user, this change was for yet unreleased rsyslog 7.5.0). [sha256 hash: 615df51cbbd6e62ed3900e1934e79c2ac02b533c01de20d28009968e54e93779]

Changelog for 7.3.14 (v7-beta)

Adiscon SupportChangelog, , , , ,

Version 7.3.14 [beta] 2013-05-06

  • bugfix: some man pages were not properly installed either rscryutil or rsgtutil man was installed, but not both Thanks to Marius Tomaschewski for the patch.
  • bugfix: potential segfault on startup when builtin module was specified in module() statement. Thanks to Marius Tomaschewski for reporting the bug.
  • bugfix: segfault due to invalid dynafile cache handling Accidently, the old-style cache size parameter was used when the dynafile cache was created in a RainerScript action. If the old-style size was lower than the one actually set, this lead to misadressing when the size was overrun, and that could lead to all kinds of “interesting things”, often in segfaults. closes: http://bugzilla.adiscon.com/show_bug.cgi?id=440

rsyslog 7.3.13 (v7-beta) released

Adiscon SupportNews, Release Announcement, , , , , ,

We have just released 7.3.13 of the v7-beta branch.

This is primarily a bug-fixing release, but also contains a new user-contributed output module for rabbitmq (provided on an as-is basis). Note that this is a BETA release, indicating that a stable version will be upcoming soon. Please test out the version and report any bugs you see.

ChangeLog:

http://www.rsyslog.com/changelog-for-7-3-13-v7-beta/

Download:

http://www.rsyslog.com/rsyslog-7-3-13-v7-beta/

As always, feedback is appreciated.

Best regards,
Florian Riedl

Changelog for 7.3.13 (v7-beta)

Adiscon SupportChangelog, , , , , ,

Version 7.3.13  [beta] 2013-04-29

  • added omrabbitmq module (contributed, untested)
    Note: this is unsupported and as such was moved immediately into the beta version.
    Thanks to Vaclav Tomec for providing this module.
  • bugfix: build problem when –enable-encryption was not selected
    Thanks to Michael Biebl for fixing this.
  • doc bugfix: omfile parameter “VeryRobustZip” was documentas as “VeryReliableZip”
    closes: http://bugzilla.adiscon.com/show_bug.cgi?id=437
    Thanks to Thomas Doll for reporting this.
Scroll to top