Open
Labels
Description
Hello,
In the latest syslog 5.0, I saw my old alert rules, so far so good, but none are processed.
Example I have rule that check for the message as SQL Expression:
`message` LIKE '%SYS-5-CONFIG_I: Configured from%'
So any change of a config, should move the message under alert.
This message should be selected:
Nov 17 08:25:27.184: %SYS-5-CONFIG_I: Configured from console by <user> on vty0 (172.21.10.94)
An using the test rule function didn't show it either.
Any path to check it why ?
And I read that some alert rules has to be moved to device alert, but I have general rule, that need to be applied for all devices.
Activity
somethingwithproof commentedon Nov 17, 2026
Your SQL expression matches in an isolated Docker instance running Syslog develop
6c8238f, PHP 8.2.35, MariaDB 11.8 and Cacti 1.2.x (bc5a1a1). I queued a message with the same%SYS-5-CONFIG_I: Configured fromtext and ran the realsyslog_process.php --debug:The message was recorded in
syslog_logsas well as the mainsyslogtable. For SQL Expression rules, “Test rule” only queriessyslog_incoming; it does not search messages already processed into the main table. A zero preview after processing does not establish that the rule failed. Filter Builder rules have a historical preview fallback, but legacy SQL rules do not.A general message rule can stay under Alert Rules. I also processed matching messages from two different hosts with the same rule and no Device Alert Rules configured. Device Alert Rules provide device handling such as muting and maintenance exceptions; this expression does not need to be moved there.
First check whether Syslog is still enabled: #458 reproduces a fatal error that makes Cacti disable the plugin, which would prevent subsequent processing. After re-enabling it, avoid “Save view defaults” until that bug is fixed. With a new matching message queued, run the following as the normal poller account, from the Cacti directory, when another Syslog processor is not running:
If it still does not alert, please share the relevant “Processing Alerts” output, any SQL errors, and the rule's enabled state, reporting method/threshold, destination and suppression/maintenance settings, with private data redacted. The matching path works in this test; the cause on your upgraded instance still needs those details.
somethingwithproof commentedon Nov 17, 2026
Related fix in #460: saving view defaults no longer disables Syslog, and SQL Expression previews now explain that they search only queued incoming messages. The general SQL alert rule matched and generated alerts in the Docker test. This issue remains open and marked unverified until we can confirm whether re-enabling Syslog resolves processing on the upgraded installation or inspect the processor output requested above.