/tags/logs/Recent content in Logs on Layer5 DocumentationHugoen/kanvas/guides/operating/log-streaming/Mon, 01 Jan 0001 00:00:00 +0000/kanvas/guides/operating/log-streaming/<p>Log streaming live-tails the output of a pod&rsquo;s containers inside the Operator canvas. Each stream starts with the most recent lines and then follows new output as it is written, so you can watch a rollout, a crash loop, or a request path next to the topology that produced it.</p> <h2 id="before-you-start" class="heading-link"> Before you start <a href="#before-you-start" class="heading-anchor" aria-label="Permalink to this heading">🔗</a> </h2> <ul> <li><strong>Operator mode on a Meshery you run.</strong> The hosted kanvas.new site does not offer Operator mode.</li> <li><strong>A connected cluster with Meshery Operator deployed.</strong> MeshSync reads the logs and Meshery Server relays them through the broker, the same path the terminal uses. See <a href="/kanvas/concepts/operator/">Operator</a>.</li> <li><strong>Containers that exist.</strong> Logs come from the Kubernetes log API, so a container that has not started has nothing to stream.</li> </ul> <h2 id="start-a-stream" class="heading-link"> Start a stream <a href="#start-a-stream" class="heading-anchor" aria-label="Permalink to this heading">🔗</a> </h2> <p>The action is named <strong>Initiate Log Session</strong> and is offered on <strong>Pod</strong> and <strong>Container</strong> resources only. Right-click the resource, or select it and use the action in the header of the Details panel. The stream opens in the same bottom-left panel as <a href="/kanvas/guides/operating/interactive-terminal/">terminal sessions</a>, as a tab.</p>/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>