Syslog 1.0 Released

[TheWitness]

All,

Syslog 1.05 is released. This Plugin Requires Cacti 0.8.7g++ and PIA 2.8++. You can find more information, and the download here: http://docs.cacti.net/plugin:syslog#syslog

TheWitness

---------------------------------------------------------------

All,

Here are some important notes/warnings.

• If you are running 0.53, or any SVN versions from Trunk, you may have to do a clean install.
• If you use the 'syslog' database, you need to edit plugins/syslog/config.php carefully before you upgrade. I have not tested using a table outside of the main 'cacti' database. Be warned!
• If your 'syslog' table is large, you might want to use the "background" option.
• This plugin is NOT compatible with PIA 1.x or 0.8.6.x
• Remove your "syslog" global.php variable before installing. This is a PIA 2.x plugin, but will detect earlier versions of Syslog and upgrade them.
• Report All Bugs and/or Feature Requests to http://bugs.cacti.net
• Remember, if you do a clean install in the 'cacti' database from the old 'syslog' database, you will need to update your syslog-ng/rsyslog configuration and restart that service
• The color arrays in plugins/syslog/config.php no longer supported. You must setup your preferred colors from Console->Settings->Syslog

Here is a brief ChangeLog.

--- 1.05 ---
bug: Remove poorly defined security settings
bug: Don't show actions if you don't have permissions
bug: Fix page refresh dropdown bug
feature: Re-add refresh settings to syslog

--- 1.04 ---
bug#0001824: Syslog icon is not shown in graph view
bug: Link on Alarm Log does not properly redirect to 'current' tab
bug: Unselecting all hosts results in SQL error
bug: Exporting to CSV not working properly
compat: Remove deprecated split() command

--- 1.03 ---
feature: Add alarm host and counts to sms messages
bug: Fix issue with individual syslog html messages
bug: Fix creating alarms and removals from the syslog tab
bug: Fix syslog removal UI with respect to rule type's

--- 1.02 ---
feature: Add syslog database functions to mitigate issues with same system installs

--- 1.01 ---
feature: Add alert commands by popular demand
bug#0001788: missing closing quote in syslog_alerts.php
bug#0001785: revision 1086 can not save reports when using seperate syslog mysql database

--- 1.0 ---
feature: Support MySQL partitioning for MySQL 5.1 and above for performance reasons
feature: Normalize the syslog table for performance reasons
feature: Allow editing of Alerts, Removal Rules and Reports
feature: Priorities are now >= behavior from syslog interface
feature: Move Altering and Removal menu's to the Console
feature: Allow specification of foreground/background colors from UI
feature: Add Walter Zorn's tooltip to syslog messages (http://www.walterzorn.com)
feature: Allow the syslog page to be sorted
feature: Add Removal Rules to simply move log messages to a lower priority table
feature: Use more Javascript on the Syslog page
feature: Add HTML e-Mail capability with CSS
feature: Display Alert Log history from the UI
feature: Allow Removal Rules to be filtered from the UI
feature: Add Reporting capability
feature: Add Instance Count Alarms
feature: Add Alert Severity to Alarms
feature: Turn images to buttons

--- 0.5.2 ---
bug: Fixes to make syslog work properly when using the Superlinks plugin
bug: Fix a few image errors

--- 0.5.1 ---
bug: More 0.8.7 Compatibility fixes

--- 0.5 ---
feature: Modified Message retrieval function to better make use of indexes, which greatly speeds it up
feature: When adding a removal rule, only that rule will execute immediately, instead of rerunning all rules
feature: Alert email now uses the Alert Name in the subject
feature: Add ability to create Reports
feature: Allow access for the guest account
feature: Change name to syslog, from haloe
feature: Use mailer options from the Settings Plugin
feature: Add option for From Email address and From Display Name
feature: Use new "api_user_realm_auth" from Plugin Architecture
bug#0000046 - Event text colors (black) when setup a event color in black
bug#0000047 - Change the Priority and Levels to be in Ascending order
bug: Fixes for errors when using removal rules
bug: Minor fix for error that would sometimes cause Syslog to not be processed
bug: Update SQL to include indexes
bug: Fix pagination of Alerts and Removal Rules
bug: Lots of code / html cleanup for faster pages loads (use a little CSS also)
bug: Fix for improper display of html entities in the syslog message (thanks dagonet)
bug: Fix Cacti 0.8.7 compatibility

I will attach some screen shots momentarily.[/list]

[TheWitness]

Here are the images I promised. This is a 'very' small setup.

TheWitness

[NetAdmin]

Larry,

I'm guessing that this could connect to an already existing syslog-ng MySQL database on the same box by modifying the config.php file. Just not sure what the settings would be to have it connect to the syslog-ng database.

Thanks in advance and nice job on this!

[TheWitness]

Yes, for the syslog_incoming for sure. However, you have to have patched lib/database.php to fix a minor compatibility issue if it's not MySQL, and you need to patch lib/functions.php to correct some additional issues around some funny AdoDB issues.

Linegod will be working up some documentation in the next week or so to address the specific howto's.

I am also soliciting feature requests here: http://bugs.cacti.net. However, I'm pretty sure the 1.0 is frozen.

TheWitness

[NetAdmin]

It's definitely a MySQL database. Will the latest SVN version of lib/functions.php be ok with 0.8.7e?

[TheWitness]

Yes, make sure you merge lib/database.php too. Make a backup of your syslog database though and use the "background" upgrade.

TheWitness

[torstentfk]

sorry for asking - but why this work on this plugin? I have tested the CAMM and loading 10 mil. syslogs is done in 10 sec, while syslog-plugin takes 4 minutes. Look and feel is for my opinion better in CAMM.
Why not put your work and CAMM work together?

Torsten

[TheWitness]

sorry for asking - but why this work on this plugin? I have tested the CAMM and loading 10 mil. syslogs is done in 10 sec, while syslog-plugin takes 4 minutes. Look and feel is for my opinion better in CAMM.
Why not put your work and CAMM work together?

Torsten

I have sent a note to gthe relative to this. The reason is that CAMM uses extJs which has a license that is not compatible with Cacti. Therefore, I can only assist him. The Cacti Groups name can not be attached to this unless we were to adopt GPLv3, which has been rejected by the members of The Cacti Group.

We revisit these things from time to time, so that may change. In the mean time, the issue with load times is likely due to a missing index. I would like to work with you to find it.

It is likely that this syslog plugin will take more time to load than CAMM. The table structure that were are using in the syslog plugin is completely normalized, which means that it will take much less space on disk. This will result in a bit of a slowdown.

TheWitness

[TheWitness]

sorry for asking - but why this work on this plugin? I have tested the CAMM and loading 10 mil. syslogs is done in 10 sec, while syslog-plugin takes 4 minutes. Look and feel is for my opinion better in CAMM.
Why not put your work and CAMM work together?

Torsten

We did an online session to determine the slowness. The problem is associated with the use of Non-Partitioned tables. When we enabled Partitioning, the performance was inline with our expectations.

TheWitness

[Hinzel]

I'm unable to run this on my system, get a number of errors. I'll post the output below.

The following shows up in my cacti log several times:
06/09/2010 11:49:01 AM - CMDPHP: Poller[0] ERROR: SQL Cell Failed!, Error:'1064', SQL:"SELECT hex FROM colors WHERE id="


I get an error on screen telling me that I don't have the settings plugin installed when I click on the "syslog" tab, even though it is installed + working.


After enabling/installing the plugin through the plugin management page, "syslog" shows up twice in the list.


Attached a few screenshots. The error message when I click on the settings tab, the duplicate entries in the plugin management screen, and the misc heading of the settings tab showing that the settings plugin is actually installed/enabled.

Any ideas/do you need anything else?

[TheWitness]

1) the hex errors can be fixed by going to settings -> syslog and hitting "save"

2) install setting 0.6

TheWitness

[michaelzhao]

ver 1.0 beta 5, setup.php

I changed:
<input name='<?php print $action;?>' type='submit' value='<?php print $value;?>>

to:

<input name='<?php print $action;?>' type='submit' value='<?php print $value;?>'>

otherwise it won't give me the "install" button.

[Linegod]

Fixed - SVN 1102.

In the future, please submit a bug report, then post bug # to forum: http://bugs.cacti.net

[TheWitness]

Thanks Jeff.

Larry

[Linegod]

Thanks Jeff.

Larry

No problem. I already had it fixed, I just forgot to commit it