Why isn't a correlation ID within one service's logs enough once a request crosses into other services?

A correlation ID only helps within one service's own log lines — once a request crosses a network call into another service, that ID needs to be propagated in an HTTP header to survive the boundary, otherwise each service's logs become an isolated island with no way to reconstruct the full request path.