/tags/observability/Recent content in Observability on Layer5 DocumentationHugoen/cloud/guides/self-hosted/planning/monitoring/Mon, 01 Jan 0001 00:00:00 +0000/cloud/guides/self-hosted/planning/monitoring/<p>Layer5 Cloud gives you four signals: two health endpoints, structured logs with stable error codes, a set of startup messages that tell you whether the deployment is fully working, and optional OpenTelemetry traces. It does not expose a Prometheus metrics endpoint, so build service-level indicators from ingress and Kubernetes metrics plus the signals below.</p> <h2 id="health-endpoints" class="heading-link"> Health endpoints <a href="#health-endpoints" class="heading-anchor" aria-label="Permalink to this heading">🔗</a> </h2> <table> <thead> <tr> <th>Endpoint</th> <th>Answers</th> <th>Meaning</th> </tr> </thead> <tbody> <tr> <td><code>GET /healthz</code></td> <td><code>200</code> with the text <code>Cloud is live</code></td> <td>The process is running. The chart uses it for the liveness probe.</td> </tr> <tr> <td><code>GET /readyz</code></td> <td><code>200</code> when ready, <code>503</code> before</td> <td>The server finished startup and is serving. The chart uses it for the readiness and startup probes.</td> </tr> </tbody> </table> <p>Both endpoints are unauthenticated. The startup probe allows 20 failed checks at 10-second intervals, so a slow start gets about 200 seconds before Kubernetes restarts the pod. Database migrations run before the server reports ready, so an upgrade that carries a large migration can approach that limit.</p>