Help and Documentation
Pulses

4min
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
|
curl --header "Content-Type: application/json" \
-H "Authorization: Bearer <your token>" \
--data '{"data": { "attributes": { "summary": "Something changed!" } } }' -X POST https://api.rootly.com/v1/pulses

curl --header "Content-Type: application/json" \
-H "Authorization: Bearer <your token>" \
--data '{"data": { "attributes": { "summary": "Something changed!" } } }' -X POST https://api.rootly.com/v1/pulses
﻿
CLI
You can create pulses through our CLI directly: https://github.com/rootlyhq/cli﻿
Linux
|
rootly pulse --api-key "ABC123" --environments "staging, production" --services "elasticsearch-staging, elasticsearch-prod" Hello World!

rootly pulse --api-key "ABC123" --environments "staging, production" --services "elasticsearch-staging, elasticsearch-prod" Hello World!
﻿
Or run a command
Linux
|
rootly pulse-run --api-key ABC123 --environments "production" --labels "version=2, attempt=1" --summary "Deploy Website" sh deploy.sh

rootly pulse-run --api-key ABC123 --environments "production" --labels "version=2, attempt=1" --summary "Deploy Website" sh deploy.sh
﻿
﻿
Updated 03 Mar 2023
Did this page help you?
TABLE OF CONTENTS
Overview
API
CLI