It’s a common thread amongst data-driven organizations: data teams face soaring volumes of data with varying complexities, which raise issues regarding data reliability. Efficiently monitoring data pipelines has become paramount to swiftly identifying and addressing potential data incidents, ensuring minimal impact on data practitioners and end users.
In software development, striking a balance between cost and quality can sometimes feel as tricky as finding a bug in a spaghetti code. Observability tools face a similar dilemma, often consuming a significant portion of the budget and growing significantly year over year. The irony? The vast majority of the data gathered is never used. As is often the case, the driving force behind this trend is not an emotional response.
In this post, we'll configure a Phoenix LiveView application to use a structured logger. We'll then use AppSignal to correlate log events with other telemetry signals, like exception reports and traces. Along the way, you'll learn about the benefits of structured logging, and you'll see how to configure a distinct framework and application logger in your Phoenix app. Let's get started!
