Product
Developers
Resources
When you experience downtime or a service interruption, it’s easy to see that something is broken. But it's never easy to see if that broken element lives at the infrastructure level or application level. Even though your observability and monitoring tools can alert you that an issue exists, their alarms typically aren’t specific enough to nail down the cause. Searching for that needle in a haystack can be a long and arduous process, causing expensive delays on the way to fixing the issue. This is especially true for any business that operates multiple Kubernetes clusters and administers systems built on top of microservices.
With so many things — in so many places — that could be broken, how do you efficiently search for the source of an issue and implement a solution?
For many, it’s an inefficient manual process. A problem occurs, and engineers then spend hours searching Stack Overflow for answers or trying a series of random commands to diagnose and repair. The worst part about this process? It’s an unreported waste of time. Most teams don’t account for time spent searching for a solution when looking holistically at how long it took to solve an issue.
Sure, manually running a command to fix an issue doesn’t take long. But recalling which commands to run — and in what order — to manually diagnose an issue is the silent killer of your team’s productivity.
Shoreline’s three-part set of Kubernetes debugging notebooks quickly scans across pods, nodes, and services to automatically diagnose issues, implement a series of repairs, and get your systems and services back up and running in no time. The three distinct notebooks (for pods, nodes, and services) can be used separately or together — allowing engineers to begin debugging a service, for example, then easily switch to a node or pod debugging sequence if relevant for the issue at hand.
With pre-built Kubernetes debugging sequences, engineers will benefit from expert-level Kubernetes knowledge and be able to make decisions and implement commands faster. Notebooks include the features listed below, yet are all completely customizable so operators can add and remove commands based on the specifics of their operating environment.
Shoreline’s Kubernetes debugging notebooks also automatically record the steps that were taken to assess and remediate a situation, removing the need for engineers to draft documentation and conduct lengthy handover meetings upon escalation.
