Syslog-ng php interface doesn't allow rule ordering
wbedard last edited by
Since the recent fix to the syslog-ng package, I have been testing it out with mixed success. While the package installs fine and starts correctly now, the flexibility of the interface used to configure the various rules seems to be missing an important feature.
In my case, I am creating separate logfiles to isolate specific traffic from the default log file, making sure to add "flags(final)" to the relevant rules, which avoids the duplication of message traffic. This works fine, provided that the syslog-ng.conf file has the rules ordered correctly, with the failover "default" rules after any user-specified ones.
What I am noticing is that the web interface has a very odd sorting behavior and the resulting config file typically has the default rules for each object type listed first. This, of course, causes all syslog traffic to be captured in the default log and relegating my custom rules as redundant. Am I misunderstanding the feature-set of the web interface for the syslog-ng package or is this a known deficiency that can be added to the "to-do" list as developer time/effort becomes available?
Thanks in advance for your consideration of this issue!