Audience member asks a compound question about observability bills and approaches for logging business-logic operations (e.g. database changes). Callaghan answers cost first: no silver bullet; OTel reduces lock-in but dashboards/alerts/UI keep switching costs high; audit and reduce what you log (his 41% bill cut, the 'okay' string logged 231M times/month); use semantic_logger's proc filter or collector exclusions; only add what you need to answer a current question; connect engineers to costs. Then domain logic: log/trace domain objects via a to_formatted_h hash.