Building an observability solution tailored to a serverless system requires data, and a lot of it. Logs, metrics, and traces are required to ensure the system can answer as many questions as possible about how it’s working, whether you’re repairing or optimizing. Each source contributes a different perspective on how your application is performing and, when analyzed together, give a complete picture of its health. Choosing an observability solution designed specifically for serverless contexts will help you reap all the benefits that serverless offers, while avoiding generic monitoring tools that might drown actionable information in a sea of metrics. A centralized dashboard provides a single pane of glass experience to monitor your entire stack from serverless functions to APIs and other services in one place, without the need to switch context or tools. Building an observability solution can be a major hidden cost in running a serverless application, but with the right tool, such as Lumigo, you can minimize these costs by focusing on service-specific data, implementing automatic instrumentation, using distributed tracing, and configuring log retention correctly.