It is tempting to treat observability as a follow-up task once a service is stable. In practice, the services that need visibility most are the new, unproven ones — which is exactly when teams are tempted to skip it.
Shipping structured logs, distributed tracing, and a baseline dashboard alongside the first deploy costs little up front and pays for itself the first time something goes wrong.