The infrastructure space is in the midst of a paradigm-shifting change. The way organizations—from the smallest of startups to established companies—build and operate systems has evolved. But as the systems we build become more distributed and (in the case of containerization) ephemeral, traditional monitoring tools have proven to be grossly insufficient. Newer tools modeled along the lines of Google and Facebook’s internal tools have emerged to meet this challenge, and given how far both SaaS and open source tools have evolved in recent years, we now have an embarrassment of observability tools to choose from.
These tools offer a great number of benefits over their predecessors, but they also bring their own set of technical and organizational challenges. Starting over from scratch isn’t a luxury most of us enjoy, and the most challenging part about modernizing one’s observability stack is iteratively evolving it. Cindy Sridharan offers an honest overview of monitoring challenges and trade-offs.
Cindy Sridharan is a Distributed Systems Engineer. Previously, she was an engineer at imgix, where she worked on API development, infrastructure, and other miscellaneous backend engineering tasks.
She likes thinking about building resilient and maintainable systems. She maintains a blog where she shares her ideas and experience about several of these topics. She is soon to be the author of a report on Distributed Systems Observability with O’Reilly.
©2017, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com