website logo
⌘K
Help and Documentation
Introduction to Rootly
Quick Start Guide
Managing Incidents
Manage Action Items
Managing Users
Managing Teams
Status Pages
Timeline
Postmortems
Playbooks
Workflows
Alerts
Pulses
Metrics
API Reference
Webhooks
Liquid
Contacting Support
Integrations
Overview
Slack
Mattermost
PagerDuty
Opsgenie
VictorOps (Splunk On-Call)
Service Now
Nobl9
Jira
Jira ( On premise )
Confluence
Confluence ( On premise )
Google Docs
Notion
Quip
Dropbox Paper
Asana
Linear
Freshservice
Trello
Shortcut ( formerly Clubhouse )
Statuspage.io
Airtable
Zendesk
Zoom
Webex
Microsoft Teams
GoToMeeting
Google Meet
Twitter
GitHub
Gitlab
AWS Elastic Beanstalk
Heroku
Kubernetes
Datadog
Honeycomb
Backstage
New Relic
Looker
Grafana
Email
SMTP
Sentry
Rollbar
Zapier
API
Terraform
Pulumi
SSO (Okta, Azure, Auth0, etc.)
SCIM
Docs powered by archbee 
4min

Pulses

Overview

Pulses represent service changes such as deploys, build completion, configuration updates, etc., providing contextual information that is critical during incident triage or hypercare.

They can be sent via specific integrations or our cli, and they do not create alerts, incidents or notifications.

API

You can create pulses through our API directly with curl for example:

Linux
|

CLI

You can create pulses through our CLI directly: https://github.com/rootlyhq/cli

Linux
|

Or run a command

Linux
|
Updated 03 Dec 2021
Did this page help you?
Yes
No
UP NEXT
Kubernetes
Docs powered by archbee 
TABLE OF CONTENTS
Overview
API
CLI