Datadog, without opening Datadog.
Ask what the graphs are doing without opening the graphs.
- Free to start
- No card
- Nothing irreversible without your yes
- 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 Datadog details, and Ray takes it from there.
@Ray is anything alerting right now?
@Ray mute the checkout latency monitor for an hour while we deploy.
@Ray what errors are in the logs for the api service since noon?
@Ray who is on call for the platform team tonight?
What Ray can and cannot do in Datadog
Reading is free, because reading changes nothing. Everyday changes Ray just makes, and anything that can't be taken back waits for your yes. The rest is not on Ray’s list.
33 reads wired, 5 actions Ray does at once, and 6 actions that wait for your yes.
Runs on its own
What Ray reads in Datadog
- Monitors and their alert state, incidents, and service checks
- Logs, metrics, traces and spans, searched or aggregated in one call
- Dashboards, SLOs, synthetic tests, hosts and APM service dependencies
- Who is on call right now, on which schedule, under which escalation policy
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Just does it
Ray does these at once
- Create or update a monitor, and create a dashboard
- Mute a monitor, or replace a host's tags
Anything Ray can put back comes with an Undo button on its reply. In a schedule, a watch or a chase that has read outside content with nobody present, these wait for a yes too.
Asks first, every time
Always waits for your yes
- Create an SLO or a synthetic API test, and update a dashboard
- Unmute a monitor, or schedule a downtime window
- Post an event to the timeline
Ray posts a card showing exactly what it is about to do. Nothing happens until someone approves, 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.
- Submit custom metrics, which would put invented numbers under your alerts
- Change on-call schedules, escalation policies or routing rules
- Delete a monitor or a dashboard, read the account's API keys, or touch webhooks
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Datadog actions that stop in the thread with the real content before they happen.
- Silence Datadog alerts for a window
- Post an event to the Datadog timeline
- Create a Datadog SLO
- Create a Datadog synthetic API test
- Unmute a Datadog monitor
- Change a Datadog dashboard
Ray does these at once
- Create a Datadog dashboard
- Create a Datadog monitor
- Mute a Datadog monitor
- Replace the tags on a Datadog host
- Change a Datadog monitor
Everyday work. Anything Ray can put back comes with an Undo button on its reply.
Silence Datadog alerts for a window
Showing Scope, Message, Start, End, Timezone, Monitor id, Monitor tags and Recurrence, each carrying the exact content that will land.
How Ray works with Datadog
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Datadog
Datadog 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
It lands, with an Undo
Reading runs on its own. Everyday changes land at once with an Undo, and anything that sends, spends or can't be taken back waits for your yes with the exact content in front of you.
Megan
@Ray the checkout bug is back. Take a look in Datadog, and tell Dana it is being looked at.
Create a Datadog dashboard
- Done
- just now
Ray uses Datadog together with the rest of your tools.
One ask can read Datadog, 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 Datadog to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Datadog and it can do the Datadog part of a request without anyone leaving the conversation: read what it needs and make the change, asking first before anything that can’t be taken back.
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.
Datadog 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 Datadog. Anything irreversible still waits for a yes.
Security and permissions
- You paste the Datadog key on Ray’s own page, never in Slack. It goes straight to the connection and never reaches the model.
- What waits for a yes is decided in the execution path, not by a prompt. No setting lets an irreversible action through without one.
- 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 Datadog in a message. Uninstall Ray and every connection it held is revoked.
Datadog and Ray, answered
The questions teams ask before they connect Datadog. 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 Datadog.
Free to start, no credit card, and nothing irreversible happens without your yes.
By adding Ray, you accept the Terms and Privacy Policy.