These technologies are battle-tested, and were adopted or replicated in Linux-land . Fore example, systemd does event logging and service management. Likewise, Linux file permissions haven't really stood the test of time, enterprise-grade systems use ACLs, which again, are a retrofit into Unix/Linux, but native to windows. For Linux, you have a choice of these implementations, but most are built on top of the OS, and each have their fanbases.
The 'traditional way' of sysadmin-style semi-custom Linux boxes, each with their own permissions setups and init scripts have thankfully gone out of vogue.
The creators of UNIX inherited the hierarchical file system of Multics, but they have abandoned ACLs, considering that they are too complicated for small mini-computers with a few users, and they have replaced the ACLs with the well known UNIX file permissions.
So ACLs are not some Windows or Microsoft innovation. Both the POSIX ACLs and the Windows NT ACLs have resurrected the Multics ACLs.
Regarding system logs and service scheduling, Windows has made only negligible improvements over UNIX.
https://blogsystem5.substack.com/p/windows-nt-vs-unix-design
From what I've read, Windows NT does have a good design underneath while Unix is simpler, but I don't think any windows version has offered the capabilities in a straightforward manner and easy to administrate. Too much awful layers as the parent comment says. While Unix has been mostly the kernel => the service manager => your service surrounded by a few concepts like users, unix sockets, file permissions,...