Other team members across the organization are repeating efforts, and your CMO is left in the dark while no updates are being sent out to the rest of the organization.Īs all of this is going on, you get texted by John in Finance about an errant table in his spreadsheet, and Eleanor in Operations about a query that pulled interesting results. However, your teams’ response to the incident is a mess.
You and your team drop what you’re doing and begin to troubleshoot the issue at hand. You wake up to messages from your CEO saying, “The numbers in this report don’t seem right…again.” It’s Monday morning, and your phone won’t stop buzzing.
#DCOMMANDER DATA HOW TO#
In a previous post, we discussed how to set up automatic detection and alerting for bad data now, we share how the best data teams handle triaging and severity assessment for your broken data pipelines with the help of an emerging role for data teams: data incident commander. With the rise of data platforms and the data-as-a-product mentality, building more reliable processes and workflows to handle data quality has emerged as a top concern for data engineers.
Incident management isn’t just for software engineers.
0 kommentar(er)
