Like many reliability investments, the value of observability often isn’t appreciated until things go wrong, so figuring out who gets the bill can be difficult. Mapping usage to specific teams is helpful, but the ever-increasing surface area of observability capabilities across tracing, logs, metrics, error tracking, real user monitoring, and more, complicates the mapping. Getting consistent terminology and buy-in on a process can take time. How do you navigate a multifaceted problem like this? Join us as we go on an Observability and FinOps journey.