Category: Software, Business, Security, Data, Architecture, firewall, automation

This is Part 2 of a two-part series on how observability design and architecture need to start with the fundamentals: keeping people and process at the center of it all. In Part 2, we cover the technology aspect of observability design and architecture, and explore “build vs. buy” and how to plan for failure.

My first question to anyone participating in this discussion is, “How much engineering time do you have to support a “build-your-own solution” vs. the cost of paying for a commercial tool?”

I prefer a mix of commercial tools such as Cribl LogStream and Splunk to form the basis of my observability pipeline.

You need your observability platform to scale to handle the spike in traffic that only occurs when the environment is under pressure and failing, such as when your firewalls are running out of CPU and logging gigs of data per second.

Related Articles