Pulses
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.
You can create pulses through our API directly with curl for example:
You can create pulses through our CLI directly: https://github.com/rootly-io/cli
Or run a command
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.com/docs/github-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.com/docs/gitlab-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 can watch different resources and create pulses:
Ready to configure Kubernetes integration ? https://rootly.io/docs/kubernetes-integration