Yes. Using loglevels/priorities, facilities and identities in a sane way, your logs would already be classified. Let's say there's a service failure and I want

Yes. Using loglevels/priorities, facilities and identities in a sane way, your logs would already be classified. Let's say there's a service failure and I want to know what the service has done prior to the failure. I wouldn't want a classifier to filter the logs in that case, so that use case is out of the picture. What other use cases than filtering are there for this? Maybe as a way to provide feedback to developers to fix the log messages, as in "this thing that we log all the time can be determined to never affect the process of trouble-shooting our services, and the classifier thinks it's noise, so we'll remove it".