An enterprise fleet telemetry application ingests real-time device metrics into Google Cloud. To minimize storage costs, the team implemented Cloud Logging exclusion filters across the project. During a recent service disruption, automated alerts failed to fire because essential application exception logs were inadvertently dropped before Cloud Monitoring could evaluate log-based alert metrics. Which configuration adjustment to the logging and alerting architecture resolves this incident management gap while maintaining cost optimization?
- Adjust the Cloud Logging exclusion filters to explicitly preserve logs with severity level ERROR and above while filtering out lower-severity informational and debug entries.Cevap
- BRemove all exclusion filters and assign the primitive Project Owner IAM role to the incident response team to allow full visibility across all project log buckets.
- CConfigure backend load balancer health checks to execute deep database queries and trigger automated alerts upon health check failure.
- DReplace log-based metrics with static single-threshold alerts on total HTTP request volume to bypass Cloud Logging entirely.
Cevap
Adjust the Cloud Logging exclusion filters to explicitly preserve logs with severity level ERROR and above while filtering out lower-severity informational and debug entries.
Refining exclusion filters to explicitly exempt logs with severity level ERROR or higher guarantees that critical failure telemetry reaches Cloud Logging and Cloud Monitoring for automated alerting, while still achieving cost optimization by excluding noise from informational logs.
Adım Adım Çözüm
Anahtar Kavram
Log Ingestion Exclusion Filters and Log-Based Alerting
Tahmini Süre:1m 30s