Monitoring setup

Monitoring setup covers two separate things: the subscription plans you sell customers (what they get, what it costs, how they sign up), and the alerts solarOS raises when a monitored system has a problem. Neither one requires the other, but most contractors set up both.

What a plan promises

A maintenance plan is what you sell: a name, a price, and always monitoring access. On top of that, a plan can promise real, trackable deliverables (an annual inspection, a panel cleaning) built from deliverable types. A plan with zero deliverables still sells and bills monitoring; it just doesn't promise anything schedulable beyond that.

A customer subscribes either through direct checkout or a plan offer (a gifted free period). Either way it creates a subscription, bound to a property. As that subscription activates and renews, its deliverables become entitlements, trackable obligations that move from Pending to Earned to Scheduled to Fulfilled (or Expired or Voided).

What must be configured before monitoring works

Monitoring alerts (device offline, underperformance, and so on) work out of the box at platform defaults; nothing is required before they start firing on a subscribed site. The Alerts & Thresholds and Notifications screens under Settings → Monitoring are there to tune sensitivity and decide who gets told, not to turn alerts on in the first place.

Selling a plan is different: it needs Payments (Stripe) connected before a plan can go active or show up in the customer-facing shop. This guide doesn't walk through connecting Stripe.

Guides in this section

• Build a maintenance plan
• Get a plan in front of customers
• Configure monitoring alerts and notifications

For the day-to-day monitoring dashboard your team works from, see Monitoring.