Grafana Cloud, without opening Grafana Cloud.
What is firing, what the logs say, and who is holding the pager.
- Free to start
- No card
- Every write waits for you
- Your own account, not a shared login
Ask in your own words.
Nothing to configure and no builder to open. Copy one of these into a thread, swap in your own Grafana Cloud details, and Ray takes it from there.
@Ray what do the api logs say about that 500 spike?
@Ray silence the disk-space alert until the migration finishes.
@Ray who is holding the pager tonight?
@Ray open an incident for the checkout outage and mark it major.
What Ray can and cannot do in Grafana Cloud
Reading is free, because reading changes nothing. Everything that writes waits for you. The rest is not on Ray’s list.
46 reads wired, 10 actions that wait for a human.
Runs on its own
What Ray reads in Grafana Cloud
- What is paging right now in OnCall, on which schedule, and who is holding it
- Incidents with their status and severity, and the notes people left on the timeline
- Dashboards, their panels, the queries behind them, and the folders they sit in
- Prometheus metrics, Loki logs and Tempo traces, queried directly or through a panel
Reading changes nothing, so Ray never stops to ask whether it may look something up.
Asks first, every time
What waits for your approval
- Acknowledging or resolving an alert that has paged someone
- Silencing an alert for a window, and editing the alert rules themselves
- Declaring an incident, moving its status or severity, and adding a note to it
- Saving a dashboard, making a folder, and annotating a panel with what happened
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.
- Reach a self-hosted Grafana, which runs its own server inside your network
- Add or edit a datasource, because both hand back the credentials behind it
- Install a plugin, change roles and permissions, or move where notifications route
Exactly what Ray will ask you to approve.
Not a category of permission. These are the Grafana Cloud actions Ray can take, each one stopping in the thread with the real content before it happens.
- Alerting manage rules
- Alerting manage silences
- Change an on-call alert
- Declare a Grafana incident
- Update a Grafana incident
- Add a note to a Grafana incident
- Save a Grafana dashboard
- Create a Grafana folder
- Annotate a Grafana dashboard
- Edit a Grafana annotation
Change an on-call alert
Showing Alert group id, each carrying the exact content that will land.
How Ray works with Grafana Cloud
No workflow to build, and nothing to maintain when the work changes.
- 01
Connect Grafana Cloud
One click, right where you asked. Ray posts a connect card, you authorise Grafana Cloud with your own account, and the work you asked for picks up where it left off.
- 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 Grafana Cloud, and tell Dana it is being looked at.
Alerting manage rules
- Waiting on
- your approval
Ray uses Grafana Cloud together with the rest of your tools.
One ask can read Grafana Cloud, 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 Grafana Cloud to Ray actually do?
Ray is an AI teammate that works in your team chat, on Slack today. Connect Grafana Cloud and it can do the Grafana Cloud 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.
Every person on the team connects their own Grafana Cloud account, so Ray can only reach what that person can already reach, and the history in Grafana Cloud shows who actually asked.
Security and permissions
- You authorise Grafana Cloud on its own login screen. Your password never passes through Ray.
- 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.
- Disconnect Grafana Cloud in a message, or uninstall Ray and every connection it held is revoked.
Grafana Cloud and Ray, answered
The questions teams ask before they connect Grafana Cloud. 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 Grafana Cloud.
Free to start, no credit card, and it asks before it acts.