Ad blocker detected: Our website is made possible by displaying online advertisements to our visitors. Please consider supporting us by disabling your ad blocker on our website.
I think I have found the problem for some of people like me. Instead to insert the trap in the syslog_incoming table we have insert it directly in the syslog .....
I will update my "syslogupd" in order to fill the incoming table (in few days).
Hey pepj,
I think its correct to log the entries into syslog table.
The logic should be:
When you receive a syslog, you will logged all into syslog table.
On top of that you will check against the syslog_alert table whether current syslog messages match any entries.
If yes, then write into syslog_incoming.
But exactly how haloe picked up from syslog_incoming table I have no idea.
DrivesMeCrazy wrote:I think its correct to log the entries into syslog table.
The logic should be:
When you receive a syslog, you will logged all into syslog table.
On top of that you will check against the syslog_alert table whether current syslog messages match any entries.
If yes, then write into syslog_incoming.
But exactly how haloe picked up from syslog_incoming table I have no idea.
No I have seen Haloe look at the syslog_incomming to check the alarms and rules(to delete) and after copy the the raimaining good traps to the syslog. (process.php file)
I will try this week-end ...
For people using my syslogupd or using text-trap-files to fill the SQL-haloe-DB, I have done some changes to function correctly with Haloe-Email and alerts.