Your example seems like it would be a great system to have access to, but it seems like that question would be formed after using a more general system like Scuba where you can iterate on the data rapidly.
The article's arguments "Look if you squint logs and traces kinda overlap" misses the point that if you want to use traces effectively you need to be able to graph them as flame-graphs and also query these relationships ("count average number of userLogin spans that failed that have a subsequent succeeding userLogin span with the same userId and same originatingIp")
To be fair even the more advanced products struggle with sophisticated queries, though splunk and sumo have usually met my needs just fine. Honestly even SQL has an order of magnitude more powerful querying than scuba.