Skip to content

Commit 97a0e1b

Browse files
committed
more info
1 parent 3abf13e commit 97a0e1b

File tree

2 files changed

+9
-6
lines changed

2 files changed

+9
-6
lines changed

src/content/changelog/durable-objects/2025-10-16-durable-objects-data-studio.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: New Durable Objects Data Studio
2+
title: Durable Objects Data Studio in Beta
33
description: Access Durable Objects stored data via Cloudflare dashboard.
44
products:
55
- durable-objects
@@ -15,8 +15,8 @@ You can now view and write to each Durable Object's storage using a UI editor on
1515

1616
<DashButton url="/?to=/:account/workers/durable-objects" />
1717

18-
Data Studio unlocks easier data accesswith Durable Objects. Before Data Studio, querying your Durable Objects data required deploying a Worker.
18+
Data Studio unlocks easier data access with Durable Objects. Before, querying your Durable Objects data required deploying a Worker.
1919

20-
To access Data Studio, you can provide an object's unique name or ID generated by Cloudflare. Data Studio requires you to have at least `Workers Platform Admin` [role](/fundamentals/manage-members/roles/), and all queries are captured with audit logging for your security and compliance needs.
20+
To access a Durable Object, you can provide an object's unique name or ID generated by Cloudflare. Data Studio requires you to have at least the `Workers Platform Admin` role, and all queries are captured with audit logging for your security and compliance needs. Queries executed by Data Studio send requests to your remote, deployed objects and incur normal usage billing.
2121

2222
To learn more, visit the Data Studio [documentation](/durable-objects/observability/data-studio/). If you have feedback or suggestions for the new Data Studio, please share your experience on [Discord](https://discord.com/channels/595317990191398933/773219443911819284)

src/content/docs/durable-objects/observability/data-studio.mdx

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ Each Durable Object can access private storage using [Storage API](/durable-obje
1414

1515
You can only use Data Studio to access data for [SQLite-backed Durable Objects](/durable-objects/best-practices/access-durable-objects-storage/#create-sqlite-backed-durable-object-class).
1616

17-
At the moment, you can only access data persisted using the [SQL API](/durable-objects/api/sqlite-storage-api/#sql-api). Key-value data persited using the KV API will be read-only in the future.
17+
At the moment, you can only read/write data persisted using the [SQL API](/durable-objects/api/sqlite-storage-api/#sql-api). Key-value data persisted using the KV API will be made read-only in the future.
1818
:::
1919

2020
## View Data Studio
@@ -30,8 +30,11 @@ You need to have at least the `Workers Platform Admin` [role](/fundamentals/mana
3030
4. Provide a Durable Object identifier, either a user-provided [unique name](/durable-objects/api/namespace/#getbyname) or a Cloudflare-generated [Durable Object ID](/durable-objects/api/id/).
3131
</Steps>
3232

33+
- Queries executed by Data Studio send requests your remote, deployed objects and incur [usage billing](/durable-objects/platform/pricing/) for requests, duration, rows read, and rows written. You should use Data Studio as you would handle your production, running objects.
34+
- In the **Query** tab when running all statements, each SQL statement is sent as a separate Durable Object request.
35+
3336
## Audit logging
3437

35-
All queries issued by the Data Studio are logged with [audit logging v1](/fundamentals/account/account-security/review-audit-logs/).
38+
All queries issued by the Data Studio are logged with [audit logging v1](/fundamentals/account/account-security/review-audit-logs/) for your security and compliance needs.
3639

37-
- Each query emits two audit logs, a `query executed` action and a `query completed` action indicating query success or failure.
40+
- Each query emits two audit logs, a `query executed` action and a `query completed` action indicating query success or failure. `query_id` in the log event can be used to correlate the two events per query.

0 commit comments

Comments
 (0)