Cloud cost modelling, build-versus-buy reasoning, and defending spend to non-technical stakeholders.
3 questions in Architecture & Tech Leadership.
Attribute observability cost by signal, service and pricing dimension. Then cut by value per byte: debug and duplicate logs at source, logs that should be counters, hot retention nobody queries. Protect audit and security logs, error events and SLO signals from sampling, and never cut by a flat percentage.
Attribute the bill before touching it, then work in order: fix the architectural decisions that generate spend, right-size against measured demand, and only commit to discounts once the shape is stable. Track a unit cost so a reduction can be told apart from a traffic drop.
Earn the right to the claim by attributing infrastructure cost per tenant, then separate cost caused by their usage shape from cost caused by your own design. Architecture can change the shape; the decision about who pays is commercial, and it needs the engineering evidence to happen at all.