work-items: probe ccr.session.id in a routine OTEL run #7595

Activity

1. kyle-sexton

   added

   needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.Human-in-the-loop required; autonomous sessions must not resolve items carrying this.

   on Oct 16, 2026
2. kyle-sexton

   added a parent issue on Oct 16, 2026

   • work-items: bug path, triage clusters, claim protocol, trackers and morning brief #7578
3. kyle-sexton

   added the

   Task

   issue type on Oct 16, 2026
4. kyle-sexton

   set

   Work status

   to

   needs-spec

   on Oct 16, 2026
5. github-actions commented on Oct 16, 2026

   

   github-actionsBot

   on Oct 16, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for the report. Automated triage handed this issue to a maintainer.

   Proposed work class: work-class: read-only
   Basis: automated intake triage; a maintainer confirms or changes it.

   _{Automated triage. A maintainer reviews it.}
6. kyle-sexton

   added

   needs-specNeeds a Brief or plan before anyone can build it.Needs a Brief or plan before anyone can build it.

   on Oct 16, 2026
7. kyle-sexton commented on Oct 16, 2026

   

   kyle-sexton

   on Oct 16, 2026

   MemberAuthor

   More actions

   Probe result: the docs say yes. The live check moves to the cost-per-item slice (owner decision, 2026-10-16).

   • Docs read 2026-10-16: the standard attributes on monitoring-usage include ccr.session.id, "Cloud session identifier, the value of CLAUDE_CODE_REMOTE_SESSION_ID, on sessions that run in a cloud environment". On metrics it is controlled by OTEL_METRICS_INCLUDE_SESSION_ID (default true). The page also says "metrics and events from a cloud session carry the standard attributes, including session.id, ccr.session.id, and organization.id".
   • Routines run as cloud sessions in a cloud environment (routines). CLAUDE_CODE_ENABLE_TELEMETRY and the OTEL_* variables go in the environment's variables or in the env block of server-managed settings, not in the setup script (cloud-environments).
   • For the mapping design: the value starts with cse_, but session URLs use session_ (cloud-environments).
   • A live probe needs two things:
     • a public OTLP collector over HTTPS on port 443, with a publicly trusted certificate and no credential;
     • a cloud environment whose network access is set to Custom, allowing only that host. The default Trusted level returns 403 host_not_allowed.
   • No routine was run and no variables were set.
   • The live check moves to work-items slice h, the only consumer: plugins/harness-ops/skills/observability/otel/cc-otel.sql already reads the attribute.
8. kyle-sexton

   closed this as completedon Oct 16, 2026