Better Stack, without opening Better Stack.
Whether it is up, who is being paged about it, and what customers are told.
- Free to start
- No card
- Every write waits for you
- One key for the workspace
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Better Stack details, and Ray takes it from there.
@Ray is checkout still down, and who is on call for it?
@Ray acknowledge the payments incident, I am looking at it.
@Ray what has uptime been on the api this month?
@Ray post a status update saying we have identified the cause.
What Ray can and cannot do in Better Stack
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
56 reads wired, 37 actions that wait for a human.
Runs on its own
What Ray reads in Better Stack
- Monitors and heartbeats, their uptime, and their response times
- Incidents with their comments and full timeline
- On-call schedules, escalation policies, and severities
- Status pages, their sections, resources, reports, and updates
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Acknowledge, resolve, or escalate an incident
- Raise an incident, or comment on one
- Create or update a monitor, a heartbeat, or the groups they sit in
- Post a status update, and build the report it belongs to
- Change escalation policies, on-call schedules, and severities
Ray posts a card showing exactly what it is about to do. Nothing happens until someone clicks approve, and no setting turns that off.
Not on the list
Things Ray is never handed
These are left out during curation, so they are not something Ray could do and decides against. They are not in front of it at all.
- Read back your Better Stack API token
- Create, edit, or read outgoing webhooks
- Reconfigure a status page, including its password
- Delete anything, from a monitor to a status update
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Better Stack actions Ray can take, each one stopping in the thread with the real content before it happens.
- Acknowledge a Better Stack incident
- Create a Better Stack escalation policy
- Create a Better Stack heartbeat
- Create a Better Stack heartbeat group
- Raise a Better Stack incident
- Comment on a Better Stack incident
- Set Better Stack metadata
- Create a Better Stack monitor
- Create a Better Stack monitor group
- Create a Better Stack on-call schedule
Acknowledge a Better Stack incident
Showing Incident id and Acknowledged by, each carrying the exact content that will land.
How Ray works with Better Stack
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Better Stack
Better Stack has no per-person login, so it takes one workspace key. Ray posts a connect card, you paste the key on Ray's own page rather than in Slack, and it covers the whole team from then on.
- 02
Ask in plain words
In the conversation you were already having. Nothing to build, no trigger to map, no tab to open.
- 03
Approve, and it lands
Reading runs on its own. Anything that creates, sends or spends stops first and shows you the exact content.
Priya
@Ray the checkout bug is back. Take a look in Better Stack, and tell Dana it is being looked at.
Acknowledge a Better Stack incident
- Waiting on
- your approval
Ray uses Better Stack together with the rest of your tools.
One ask can read Better Stack, cross-reference what is in these, and land the finished result back in the thread. Not four connectors taking turns, one teammate with one memory.
What does connecting Better Stack to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Better Stack and it can do the Better Stack part of a request without anyone leaving the conversation: read what it needs, draft the change, and post it for approval before anything is written.
It is not a workflow builder. There is no trigger to configure and no automation to repair when your process shifts. You describe the outcome in the thread and Ray picks the actions, including actions in your other connected tools when the request spans more than one.
Better Stack has no per-person login, so it connects once with a single workspace key and covers the whole team. Ray reaches whatever that key reaches, which is worth scoping the way you want everyone to see Better Stack. Every write still stops for approval first.
Security and permissions
- You paste the Better Stack key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
- Writes are gated in the execution path, not by a prompt. There is no setting that grants blanket approval.
- Each workspace is isolated at the database level, and that isolation is tested by trying to break it.
- An admin, or whoever connected it, can disconnect Better Stack in a message. Uninstall Ray and every connection it held is revoked.
Better Stack and Ray, answered
The questions teams ask before they connect Better Stack. Every answer is how this integration is built rather than a promise about it.
More dev & deploys integrations
Ray uses them together in a single run when a request spans more than one.
Put Ray to work in Better Stack.
Free to start, no credit card, and it asks before it acts.
By adding Ray, you accept the Terms and Privacy Policy.