[DOCS] Monitoring usage docs omit `app.entrypoint` metric attribute and `OTEL_METRICS_INCLUDE_ENTRYPOINT`

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/monitoring-usage

Section/Topic

"Metrics cardinality control" and "Standard attributes"

Current Documentation

The monitoring page currently says:

The following environment variables control which attributes are included in metrics to manage cardinality: | OTEL_METRICS_INCLUDE_SESSION_ID | Include session.id attribute in metrics | true | false | | OTEL_METRICS_INCLUDE_VERSION | Include app.version attribute in metrics | false | true | | OTEL_METRICS_INCLUDE_ACCOUNT_UUID | Include user.account_uuid and user.account_id attributes in metrics | true | false |

Later on the same page it says:

All metrics and events share these standard attributes: | session.id | Unique session identifier | OTEL_METRICS_INCLUDE_SESSION_ID (default: true) | | app.version | Current Claude Code version | OTEL_METRICS_INCLUDE_VERSION (default: false) | | organization.id | Organization UUID (when authenticated) | Always included when available | | user.account_uuid | Account UUID (when authenticated) | OTEL_METRICS_INCLUDE_ACCOUNT_UUID (default: true) | | user.account_id | Account ID in tagged format matching Anthropic admin APIs (when authenticated), such as user_01BWBeN28... | OTEL_METRICS_INCLUDE_ACCOUNT_UUID (default: true) | | user.id | Anonymous device/installation identifier, generated per Claude Code installation | Always included | | user.email | User email address (when authenticated via OAuth) | Always included when available | | terminal.type | Terminal type, such as iTerm.app, vscode, cursor, or tmux | Always included when detected |

The environment variables reference currently lists:

| OTEL_METRICS_INCLUDE_ACCOUNT_UUID | Set to false to exclude account UUID from metrics attributes (default: included). See Monitoring | | OTEL_METRICS_INCLUDE_SESSION_ID | Set to false to exclude session ID from metrics attributes (default: included). See Monitoring | | OTEL_METRICS_INCLUDE_VERSION | Set to true to include Claude Code version in metrics attributes (default: excluded). See Monitoring |

What's Wrong or Missing?

The docs do not mention the new opt-in metric attribute introduced in v2.1.152.

A. Missing cardinality-control variable

OTEL_METRICS_INCLUDE_ENTRYPOINT=true is not documented on the monitoring page or in the environment variables reference, so admins cannot discover how to enable the attribute.

B. Missing standard metric attribute

The monitoring page's standard-attributes table does not mention app.entrypoint, even though the changelog for v2.1.152 says Claude Code now adds it to metrics when the opt-in variable is enabled.

Suggested Improvement

Update the OpenTelemetry docs to document the new metric attribute and its opt-in flag.

Minimum fix:

1. Add OTEL_METRICS_INCLUDE_ENTRYPOINT to the "Metrics cardinality control" table on monitoring-usage with its default behavior and enable value.
2. Add app.entrypoint to the "Standard attributes" table with a note that it is emitted only when OTEL_METRICS_INCLUDE_ENTRYPOINT=true.
3. Add the same environment variable to env-vars so admins searching the env var reference can find it.
4. Briefly explain what values app.entrypoint can contain, for example whether it identifies CLI vs SDK vs other session entry paths.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/monitoring-usage | 107-115 | Metrics cardinality control table omits OTEL_METRICS_INCLUDE_ENTRYPOINT |
| https://code.claude.com/docs/en/monitoring-usage | 381-393 | Standard attributes table omits app.entrypoint |
| https://code.claude.com/docs/en/env-vars | 319-321 | Env var reference lists the other OTEL_METRICS_INCLUDE_* variables but not OTEL_METRICS_INCLUDE_ENTRYPOINT |

Related changelog note: In v2.1.152, the changelog says: "Added the session entrypoint as an OpenTelemetry metric attribute (app.entrypoint, opt-in via OTEL_METRICS_INCLUDE_ENTRYPOINT=true)".

Total scope: 2 documentation pages affected, plus the changelog already references the feature.