A cloud operations team wants to reduce overall Cloud Logging ingestion and storage costs by filtering out non-essential debug logs before they are written to the default log bucket, while preserving high-severity error logs for operational monitoring. Which approach aligns with Google Cloud recommended practices for controlling log ingestion costs?
- Configure a log exclusion filter in the log router sink specifying severe or error severity levels to be retained while excluding debug entries.Cevap
- BCreate an aggregate log exclusion filter that drops all log entries originating from virtual machine resources regardless of severity level.
- CAssign the primitive Viewer role to all instance service accounts to limit their authority to transmit logs to Cloud Logging.
- DDeploy a VPC Service Controls perimeter around Cloud Logging to prevent debug log entries from traversing network interfaces.
Cevap
The optimal approach is to configure a log exclusion filter in the log router sink that targets debug-severity log entries while keeping high-severity entries.
Configuring exclusion filters in the log router allows organizations to drop specific low-priority logs like debug records before they enter log buckets, effectively reducing ingestion and storage costs while retaining vital error logs.
Adım Adım Çözüm
Anahtar Kavram
Cloud Logging Log Router Exclusion Filters