2 years ago

https://www.linkedin.com/in/brandonlandry24/ Sifting through the sheer volume of information for Kubernetes troubleshooting, even with the help of today’s observability tools, is still like finding a needle in a haystack. Traditional monitoring and observability tools using open source data collectors are inherently flawed as the data feeding them is incomplete. Failures generally consist of many individual events (more on this below), building on each other to make up a larger failure sequence.

Not to mention, these tools are reactive, prompting the user if there is an issue, after something went wrong.

As one event in a sequence occurs in a Kubernetes cluster, a “strand” of the DNA is filled out.