Having worked with both monolithic and SOA apps, the later yields radically simpler architectures and from there you spend a lot less time debugging.
The older I grow as a programmer, the more I dislike monoliths. I'd rather have simpler programs where entire classes of bugs are guaranteed never to happen. I have yet to see a single monolithic app without serious technical and conceptual debt. The worst thing is that back when I thought monoliths were great I had absolutely no idea things could be so much simpler.
Also, HTTP/1.1 is a fantastic protocol. Its dead-simple to implement, debug, cache, send through proxies who won't understand your custom headers or body format and whatnot. It even gives you an extra layer of routing on top of TCP/IP! This is exactly what you want to build systems with.
Add the fact that high performance HTTP servers and clients exist in most languages, and building an RPC protocol on top of HTTP sounds pretty attractive. No wonder gRPC did exactly that.
You log to a central store such as an ELK stack or any of the great third party offerings. When you need to see the entire stack trace you search by the id.
If we can find a way of running a giant monolithic app in development and production environment without vertically scaling our machines, I would rather have that.
Every bug I'm working on is like a mystery that I have to hop to many services to find what's going.
I also think HTTP is the worst protocol for apps to talk to each other.