A transit-pass microservice on OKE writes helpful errors to stdout, but Logging still shows nothing from the app. Which path correctly gets those lines into OCI Logging?
Select an answer to reveal the explanation.
Short Explanation
On OKE, stdout lands on the node’s container-log path; a custom log plus the Unified Monitoring Agent is the broom that sweeps those lines into Logging. A private untailled file stays invisible.
Full Explanation
OKE application processes write to stdout/stderr; the node holds those lines under the configured container-log path. You then create a custom log plus a Unified Monitoring Agent configuration that reads that path on managed or self-managed nodes. A private file inside the container that nothing tails is invisible to Logging. Metrics-only setup and Functions invocation logs do not collect OKE app stdout for you.