> The design of hiding everything
And that is the problem. The concept of hiding log messages is a troubleshooting and security nightmare. For example, when MongoDB fails to start, systemd decides to eat the error messages. For example, on our server the output from "journalctl -u mongod" contained:
Feb 08 03:48:37 systemdtest systemd[1]: Starting SYSV: Mongo is a scalable, document-oriented database....
Feb 08 03:48:38 systemdtest runuser[28281]: pam_unix(runuser:session): session opened for user mongod by (uid=0)
Feb 08 03:48:38 systemdtest mongod[28275]: Starting mongod: [FAILED]
Feb 08 03:48:38 systemdtest systemd[1]: mongod.service: control process exited, code=exited status=1
Feb 08 03:48:38 systemdtest systemd[1]: Failed to start SYSV: Mongo is a scalable, document-oriented database..
Feb 08 03:48:38 systemdtest systemd[1]: Unit mongod.service entered failed state.
It logs that it failed to start, but systemd threw away the reason. Using strace I was able to find-out that it was a SELinux setup issue. The problem was that /var/lib/mongo somehow lost the mongod_var_lib_t security context. Doing a restorecon fixed the problem. That problem takes a few seconds to fix with standard syslog. With systemd's policy against logging, it took me over half of a day. This is why systemd is evil.
Even worse is if you have a security problem then systemd makes it much harder to find-out what happened because it throws away so much logging.