Model data control flow in logs
We're using syslog as the generalized transport for asynchronous messages, at least those that are expected to end up in a searchable database somewhere -- so it would be nice to be able to model these data flows explicitly (switching on log_type attribute, for instance?) and describe them in a way that float would understand, and configure the system accordingly.
In line with this thinking, it would be nice to be able to set up log consumers that are not searchable databases, for example for the purpose of log watching (for periodic / real-time analysis, or alerting)...