Pulses

Last update: July 15, 2021

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:

curl --header "Content-Type: application/json" \
-H "Authorization: Bearer <your token>" \
--data '{"data": { "attributes": { "summary": "Something changed!" } } }' -X POST https://api.rootly.io/v1/pulses
CLI

You can create pulses through our CLI directly: https://github.com/rootly-io/cli

rootly pulse --api-key "ABC123" --environments "staging, production" --services "elasticsearch-staging, elasticsearch-prod" Hello World!


Or run a command

rootly pulse-run --api-key ABC123 --environments "production" --labels "version=2, attempt=1" --summary "Deploy Website" sh deploy.sh
GitHub Integration

Rootly will automatically add the following GitHub events as pulses:

  • Push to any repositories
  • Merged pull requests
  • More to come...

Ready to configure GitHub integration ? https://rootly.io/docs/github-integration

Gitlab Integration

Rootly will automatically add the following Gitlab events as pulses:

  • Push to any repositories
  • Merged pull requests
  • More to come...

Ready to configure Gitlab integration ? https://rootly.io/docs/heroku-integration

Heroku Integration

Heroku will automatically add the following Heroku events as pulses:

  • A build starts
  • A build ends ( Failed or succeeded )
  • A release is deployed
  • More to come...

Ready to configure Heroku integration ? https://rootly.io/docs/heroku-integration

Kubernetes Integration

Kubernetes integration can watch different resources and create pulses:

Ready to configure Kubernetes integration ? https://rootly.io/docs/kubernetes-integration