Monitoring changedcowork/monitoring
Nearest release: v2.1.321, published 4 hours after upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 9 Nov 2026 14:40 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 9 Nov 2026 15:07 UTC.
Upstream edited
Recorded here
Lines+18added
Lines−13removed
From line
12
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits12to this page, all time
The whole hunk
from line 12, old and new numbered
/
from line 12
1212
1313## Setup
1414
15Configure monitoring from the Cowork admin settings:
15Configure monitoring from **Organization settings > Data and privacy**:
1616
171. Navigate to **Admin settings > Cowork**
171. Go to **Organization settings > Data and privacy**
1818
192. Configure the following fields:
192. Under **Monitoring**, find the **Cowork and Cowork in the cloud** item
2020
213. Configure the following fields:
22
2123 | Field | Description | Example |
2224 | - | - | - |
2325 | **OTLP endpoint** | Your OpenTelemetry collector URL | `http://collector.example.com:4318` |
2426 | **OTLP protocol** | Transport protocol | `http/json` or `http/protobuf` |
2527 | **OTLP headers** | Authentication headers for your collector | `Authorization=Bearer your-token` |
28 | **Resource attributes** | OTel resource attributes attached to exported events | `deployment.environment=prod,team=platform` |
2629
273. Save your settings
304. Save your settings
2831
294. Start a new Cowork session — settings are loaded at session start, so existing sessions won't pick up the new configuration
325. Start a new Cowork session — settings are loaded at session start, so existing sessions won't pick up the new configuration
3033
3134> [!NOTE]
3235>
33> The OTel exporter runs inside the Cowork VM, so it is subject to the session's egress rules. If your organization restricts network egress, Cowork automatically adds your collector's hostname to the session's egress allowlist. You don't need to add it at **Admin settings > Capabilities > Network egress**.
36> By default, Cowork runs the OTel exporter on the user's device and sends events over that device's network connection. Make sure your collector is reachable from users' devices.
37>
38> You don't need to add your collector to the **Additional allowed domains** field in **Organization settings > Capabilities**. If sessions run in the Cowork VM and your organization restricts network egress, Cowork adds your collector's hostname to the session's allowlist for you.
3439
3540## Events
3641
No line in this hunk matches that.