Closed jpobeda closed 6 years ago
I was wrong, that was a valid query but it always throws an error because if you create your rule to match host_id it builds queries for both 'syslog' table and 'syslog_incoming'. Being host_id valid for 'syslog' but not for syslog_incoming. It actually processes the valid query but fails in the other one.
So I guess we could chuck a note or description to warn users on how this works and what to expect.
Closing.
Hi, I'm opening this as a bug to not mess up https://github.com/Cacti/plugin_syslog/issues/9 issue.
At the end what I thought it was the syslog table, was the syslog database name.
I'm getting this error by simply adding a new alert rule using 'hostname is'. I'm surprised nobody else has got this issue.
So I think there shouldn't be an space between the two if we intend to query FROM database.table, right?