The rise of DevOps and Agile over the past few years has led to a shift in responsibilities. Gone are the days when troubleshooting Kubernetes issues rested solely in the hands of DevOps teams. Today, developers are expected to own their code and will find themselves on-call to troubleshoot their apps if an issue arises.
This poses a question, however: Are developers equipped with the right tools to effectively manage the troubleshooting process? After all, many of the tools they rely on to figure out root causes were initially built with DevOps teams in mind.
Join Baruch Sadogursky, head of DevOps advocacy at JFrog and Itiel Shwartz, CTO and co-founder at Komodor as they discuss: