Topic 1 Question 139
Your company runs services by using Google Kubernetes Engine (GKE). The GKE dusters in the development environment run applications with verbose logging enabled. Developers view logs by using the kubectl logs command and do not use Cloud Logging. Applications do not have a uniform logging structure defined. You need to minimize the costs associated with application logging while still collecting GKE operational logs. What should you do?
Run the gcloud container clusters update --logging=SYSTEM command for the development cluster.
Run the gcloud container clusters update --logging=WORKLOAD command for the development cluster.
Run the gcloud logging sinks update _Default --disabled command in the project associated with the development environment.
Add the severity >= DEBUG resource.type = "k8s_container" exclusion filter to the _Default logging sink in the project associated with the development environment.
ユーザの投票
コメント(3)
- 正解だと思う選択肢: D
right answer
👍 4Jason_Cloud_at2023/10/26 - 正解だと思う選択肢: D
D The idea is to prevent/minimize container logs from getting sent to the sink,
👍 2lelele20232023/11/01 - 正解だと思う選択肢: D
To minimize costs associated with application logging in Google Kubernetes Engine (GKE) while still collecting operational logs, the recommended approach is (option D).
Add the severity >= DEBUG resource.type = "k8s_container" exclusion filter to the _Default logging sink in the project associated with the development environment.
This filter excludes logs with a severity level of DEBUG or lower for the specified resource type, "k8s_container," effectively reducing the volume of verbose application logs being ingested into Cloud Logging.
This allows you to focus on collecting GKE operational logs while excluding less critical and potentially costly application logs. It helps strike a balance between maintaining visibility into operational aspects and optimizing costs associated with log storage and processing.
👍 1xhilmi2023/12/06
シャッフルモード