Continuing from my previous blog on the series, What you can’t do with Kubernetes network policies (unless you use Calico), this post will be focusing on use case number five — Default policies which are applied to all namespaces or pods.
Before I stumbled into the tech industry (a story for another day), I spent several years in the customer service world as a server and front-of-house manager in restaurants. It was in these jobs that I first honed some critical skills that would later lead me on the path to incident response.
Lumigo is excited to announce its microservice troubleshooting platform now provides developers and DevOps with the power of OpenTelemetry (OTel) with a single click. Lumigo has long been the leading troubleshooting platform for serverless, but now, users can harness its best-in-class debugging and observability platform for all microservices-based environments.
As we continue to navigate the ongoing evolution of the observability landscape, Logz.io is constantly striving to provide our customers with the advanced platform capabilities needed to make sense of their increasingly complex environments. Sometimes that means taking a new approach to long-standing practices.
You probably have seen ads where someone claims that their app can save you money by finding subscriptions you forgot about. I have a hard time imaging someone with $100s of dollars of expenses they forgot about, but I have had the occasional one that was missed. The problem is that people are inefficient when it comes to managing “stuff”. That is why there are so many places to store “stuff”.
Incidents almost never happen in a vacuum. When you receive an alert about a potential issue, odds are pretty good that you’ll need to navigate between different tools and teams to get things resolved. Of course, timing is critical in these situations, so the easier it is to communicate — between both tools and teams — the better off you’ll be.
