1Z0-1067-25 Question 116
Single answerYou are responsible for an internal business application running on Oracle Container Engine for Kubernetes (OKE). You recently enabled OCI Logging for your microservices but notice that no logs are being ingested into the Logging service. The microservices are generating logs as expected, but the logs never appear in the OCI console. Which action should you take first to resolve this issue?
- A
Confirm that the correct Log Type (Service, Custom, or Audit) is selected in OCI Logging for your OKE cluster
- B
Create a Service Connector to route logs from the Logging service to the Monitoring service
- C
Adjust the logging level inside your application code to DEBUG or TRACE and redeploy the microservices
- D
Ensure that the OKE worker nodes have the OCI Logging plugin agent installed and configured
Show answer and explanation
Correct answer: A
Explanation
To successfully implement Observability for microservices running on OKE, you must configure the appropriate Log Type within the Logging service to ensure logs from your pods and containers are properly collected. Oracle documentation emphasizes the importance of specifying the correct Log Type (Service, Custom, or Audit) based on the source of the logs. Once the right type is selected and logging is enabled, you can then use additional features like log search, analytics, or service connectors to route logs to other destinations for deeper analysis. Refer to the OCI Logging documentation for detailed steps on configuring log sources and types.
- A. Correct.
Option 1: CORRECT. When using OCI Logging with microservices running in OKE, you must configure the logs for each workload and confirm the appropriate Log Type is enabled. If the wrong type (e.g., Audit instead of Service) is selected, logs may not be ingested. Carefully verifying and selecting the correct Log Type in the Logging service helps ensure logs from your containers are properly collected.
- B. Incorrect.
Option 2: INCORRECT. A Service Connector is typically used to move data between OCI services (e.g., from Logging to Object Storage or Logging Analytics), not to enable initial log ingestion. Logging must first receive the logs correctly before a Service Connector can route them elsewhere.
- C. Incorrect.
Option 3: INCORRECT. Adjusting application logging levels might provide more log detail, but it does not directly address the ingestion issue into the OCI Logging service. If Logging is not properly configured, logs won't appear regardless of verbosity.
- D. Incorrect.
Option 4: INCORRECT. The OCI Logging Fluentd plugin agent is automatically managed when deploying to OKE with standard configurations. Manually installing the OCI Logging plugin agent is typically not required for managed OKE environments unless you�re using specialized custom node images.