Getting Started

Learn how to get started with Shoreline to handle auto-remediation and real-time troubleshooting effectively.

This guide will quickly get you up to speed on the core concepts of Shoreline, important terminology, and how you can begin using the platform in your environments.


The custom-built, operations-oriented language called Op powers most of Shoreline. Use the Op CLI and many effective Op commands -- or even pre-configured Op Packs -- to begin configuring Shoreline's auto-remediation throughout your collection of Resources.

Resources are your hosts, pods, and containers connected to Shoreline. Shoreline monitors all of your Resources using a minimal Agent process running on each host node.

Agents monitor the host and all related pods and containers to collect a vast array of data. The gathered data is periodically sent to Shoreline's backend and is used by Metrics.

Metrics are Op commands that explore the abundance of data from your Resources. Shoreline has over 150 standard Metrics and the ability to create your own via Metric queries. Metric queries are the most common way to fire Alarms.

Alarms frequently check the Metrics and other assigned Resource statuses, based on the Alarm's customizable Resource query. When an Alarm fires, it may automatically trigger Actions.

Actions execute shell commands within assigned Resources. Alarms and Actions are typically associated via Bots.

Bots connect Alarms and Actions together thereby closing the entire auto-remediation loop of Shoreline. A fired Alarm typically triggers one or more Actions through their shared Bot.

That is the high-level picture of how Shoreline integrates with your entire fleet to provide efficient, automatic remediation.

Next Steps

Below are the recommended first steps to get your feet wet with Shoreline.