1Z0-997-25 Question 159
Single answerYour organization has deployed a series of microservices on an Oracle Container Engine for Kubernetes (OKE) cluster. The team needs a centralized solution for collecting, storing, and analyzing logs from all containers, specifically wanting to run advanced searches for unique error codes and usage trends. Which approach should you implement on Oracle Cloud Infrastructure (OCI) to meet this requirement?
- A
A. Directly stream container logs to an external open-source repository hosted on a separate Compute instance, then manually import those logs into Logging Analytics.
- B
B. Configure OCI Logging for container logs, create a Service Connector to route logs to Logging Analytics, and set up log queries within Logging Analytics.
- C
C. Create a custom script on each node to export container logs as files to an OCI Block Volume, and periodically run a batch process to parse them in Logging Analytics.
- D
D. Enable Access Logs in the Load Balancer service and rely on the Access Log data alone for the entire container environment� log analysis.
Show answer and explanation
Correct answer: B
Explanation
The best practice for centralized log collection in OCI is to configure OCI Logging for container logs and use a Service Connector to forward logs to Logging Analytics. This approach ensures real-time, automated ingestion of logs for advanced searching, correlation, and analytics. For more information, refer to the Oracle Cloud Infrastructure Observability and Management documentation, specifically the sections on OCI Logging and Logging Analytics configuration.
- A. Incorrect.
Option A: Incorrect. Streaming logs to an external open-source repository on a Compute instance may work for temporary storage, but it does not fully leverage OCI Observability services. You would still have to manually import logs into Logging Analytics, which complicates automation and central management.
- B. Correct.
Option B: Correct. Using OCI Logging for container logs, then routing them to Logging Analytics via Service Connector Hub, is the recommended approach. This method centralizes container logs automatically and enables advanced filtering, correlating, and searching capabilities in Logging Analytics.
- C. Incorrect.
Option C: Incorrect. Writing container logs onto Block Volumes and parsing them with a batch process adds unnecessary complexity. It lacks the near real-time observability that Logging Analytics provides through direct ingestion from the Logging service.
- D. Incorrect.
Option D: Incorrect. Load Balancer Access Logs only capture HTTP traffic details, not the full set of application-level logs from all containers. Relying solely on Access Logs does not provide comprehensive coverage of all container events.