hard20 pts · first answer countsobservabilitycost-optimization

Logging bill tripled

The observability bill tripled after several services turned on debug logging and verbose health-check logs. Which plan cuts cost while keeping what you need for incidents?

A.Turn off all application logging and rely only on metrics and traces for every future incident.B.Keep every log line, but compress the files with gzip on each node before they are shipped.C.Move all logs to the premium hot tier so queries run faster and engineers can fix issues sooner.D.Drop or sample noisy logs at the collector, set per-environment levels, and tier old logs to cheap storage.

Discussion 0

Join free to post in the discussion.

Logging bill tripled

Discussion 0

Related questions