Monitors launch

Write Trestle's announcement email for the launch of Pipeline Monitors. Cover the facts below.

Pipeline Monitors are now available in every Trestle workspace. They watch CI pipelines the way an uptime service watches a website, and open a Trestle issue when something goes wrong.

Headline: Pipeline Monitors are now available.

Hero: a product screenshot of the Monitors tab sits under the headline and intro, spanning the content column. Reference artwork: assets.illustrations.pipelineMonitorsHero

Two calls to action sit with the hero: a primary button that reads "Read the docs" and links to https://trestle-email.s3.amazonaws.com/docs/monitors, and a secondary text link that reads "See pricing" and links to https://trestle-email.s3.amazonaws.com/pricing

What's new, two monitor types:

• Uptime monitors check a deploy preview or service URL every 1, 5, or 15 minutes and open an issue after two consecutive failed checks.
• Cron monitors track scheduled pipeline jobs such as nightly builds and release trains, and open an issue when a run is missed or overruns its expected duration.

Alert rules handle routing. One alert rule can be attached to many monitors, and each rule delivers to email, chat, or on-call paging, so routing is configured once and reused.

What to expect: existing pipeline failure notifications have been migrated as alert rules with no action required. Monitors live in a new Monitors tab in every project (https://trestle-email.s3.amazonaws.com/monitors). Every workspace includes 10 monitors at no charge; additional monitors are $2 per monitor per month.

Closing: questions go to the help center at https://trestle-email.s3.amazonaws.com/help. The email is signed by the Trestle Team.

The footer names Trestle, Inc., gives the postal address 418 Span Street, Portland, OR 97209, and links to Privacy at https://trestle-email.s3.amazonaws.com/privacy, Terms at https://trestle-email.s3.amazonaws.com/terms, and Unsubscribe at https://trestle-email.s3.amazonaws.com/unsubscribe

Use /world/trestle-email for brand chrome and CSS (the product family). Use the absolute HTTPS URLs from tokens.json; do not use /world/ paths as image src.

Dark mode should be supported.

Leave the HTML in output/email.html, a plain-text version in output/email.txt, and the subject in output/meta.json as {"subject": "..."}. Don't include From, To, or Date headers.