Shoreline.io announced Shoreline’s open source solutions library, a collection of Op Packs that make it easier to diagnose and repair the most common infrastructure incidents in production cloud environments.
Launching with over 35 Op Packs freely available to the community, the solutions library addresses issues like JVM memory leaks, filling disks, rogue processes, and stuck Kubernetes pods, among others.
Published and provisioned as open source Terraform modules, each Op Pack contains everything necessary to solve a specific issue, including pre-defined metrics, alarms, actions, bots, scripts, and tests. With Shoreline’s Op Pack library, the community identifies what to monitor, what alarms to set, and what scripts to run to complete the repair. All Op Packs are completely configurable and allow cloud operations teams to decide whether to use full automation or an interactive Notebook for human-in-the-loop repair. Co-developed with Shoreline customers, the Op Packs available at launch are based on real world on-call experience at large enterprises, rapidly growing unicorns, and the largest hyperscalar production environments.
"We're all working in the same cloud environments, yet every company has to figure out on their own how to automate even commonplace issues, like filling disks or JVM memory leaks,” said Anurag Gupta, co-founder and CEO of Shoreline. “Companies can no longer afford to write their own runbooks or custom code automations from scratch. With Shoreline, every time someone in our community fixes a problem, everyone else benefits.”
The following Op Pack solutions are immediately available, and free to Shoreline customers. The solutions library will continue to grow each month as new Op Packs are added by the Shoreline community. With each additional Op Pack in use by a customer, time is freed up for engineers to focus on innovation, rather than repetitive, mundane tasks that are better handled through automation. Op Packs available at launch include:
■ Streamline Kubernetes Operations
- Kubernetes node retirement - Gracefully terminate nodes when marked for retirement by the cloud provider.
- Kubernetes pod out of memory (OOM) - Generate diagnostic information and restart pods that ran out of memory.
- Kubernetes pods stuck in terminating - Identify, safely drain, and restart stuck pods.
- Kubernetes pods restarting too often - Detect pod restart loops and capture diagnostics to identify the root cause.
- IP exhaustion - Clear away failed jobs or pods that are consuming too many IP addresses.
- Stuck Argo workflows - Argo makes declaratively managing workflows easy, but it can leave behind many stale pods after workflow execution that should be deleted.
■ Reduce Toil (on both VMs or Kubernetes)
- Disk resize / disk clean - Disk full incidents can lead to wide-spread outages and data loss that can damage customer experiences and lose revenue.
- Networking issues - Network related issues are often hard to diagnose, and can lead to a very bad experience for customers.
- Intermittent JVM issues - Capture diagnostic information for intermittent issues that are hard to reproduce and debug.
- Server drift - Restore uniformity when configuration files, databases, and data sources on your VMs and containers differ.
- Config drift - Ensure observed state matches desired state on your system configuration, e.g. Kubernetes yaml, Cloud config, etc.
- Memory exhaustion - Running out of memory rapidly degrades customer experience and must be pre-empted.
- Disk failures in kern.log - Detect when a disk has errors or has entirely failed by inspecting the OS’s kern.log. Automatically capture these events and kick off fixes such as recycling the VM.
- Network failures in kern.log - Detect when a network interface has errors or has entirely failed by inspecting the OS’s kern.log. Automatically capture these events and initiate fixes such as recycling the VM.
- Endpoints unreachable - Determine when there are no endpoints behind your Kubernetes service or these endpoints have become unreachable.
- Elastic sharding replica management - Determine when your elastic search clusters have too few replicas per shard, and automatically kick off healing.
- Log processing at the edge - Analyze log files on the box to identify issues that cause production incidents, and eliminate costs of centralized logging.
- Kafka data Processing Lag - Restart slow/broken consumers when systems are falling behind in processing messages through a queue.
- Kafka topic management - When the length of your Kafka topic is too long, applications may begin to break.
- Processes consuming too many resources - Determine if the system is using too much memory or CPU at the process level.
- Restart CoreDNS service - CoreDNS, the default Kubernetes DNS service, can degrade in performance with too many calls causing massive latency.
■ Avoid Major Outages
- Certificate rotation - Sooner or later every company gets bitten by expired certificates and when they do, it can cause a catastrophic outage.
- DNS lag - Trigger rolling restarts of the DNS servers when they are responding slowly and causing widespread system issues.
Companies around the world rely on Shoreline’s incident automation platform to resolve common incidents in production, broaden the team that can safely repair incidents, and perform live site debugging of new incidents. Pairing this Op Pack solutions content with the Shoreline platform accelerates time to value and increases ROI for Shoreline customers.
The Latest
In the world of digital-first business, there is no tolerance for service outages. Businesses know that outages are the quickest way to lose money and customers. For smaller organizations, unplanned downtime could even force the business to close ... A new study from PagerDuty, The State of AI-First Operations, reveals that companies actively incorporating AI into operations now view operational resilience as a growth driver rather than a cost center. But how are they achieving it? ...
In live financial environments, capital markets software cannot pause for rebuilds. New capabilities are introduced as stacked technology layers to meet evolving demands while systems remain active, data keeps moving, and controls stay intact. AI is no exception, and its opportunities are significant: accelerated decision cycles, compressed manual workflows, and more effective operations across complex environments. The constraint isn't the models themselves, but the architectural environments they enter ...
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...