[pauldambra]

Why

SDK maintainers need one clear Metrics contract and support record for network request timing. This prevents Session Replay support from being reported as Metrics support.

Changes

• Adds Network Request Timing requirements directly to the Metrics spec, and archives the change.

• Defines safe data handling and separates verified SDK support from future candidates.

• Fixes the Metrics spec so strict validation passes (a NUL byte and one requirement wording).

Depends on #30.

---

Created with PostHog from a Slack thread

[marandaneto]

we dont use the sdk-specs as RFC but rather the already approved/agreed spec so make sure this PR archives the current spec and change the spec directly in the PR
eg https://github.com/PostHog/sdk-specs/pull/64/changes
the current spec goes to change/archive
the new spec is updated
https://github.com/PostHog/sdk-specs/tree/main/.agents/skills has the skills you need

[pauldambra]

🤖 (robot reply on behalf of @pauldambra)

Thanks @marandaneto. Done in 3414b36:

• The change is archived to openspec/changes/archive/2026-11-06-add-network-request-metrics/.
• The new requirements are synced directly into openspec/specs/metrics/spec.md.

I also fixed the Validate specs check. The metrics spec from #30 had a literal NUL byte and one requirement without SHALL on its first line. openspec validate --specs --strict now passes locally.

[pauldambra]

🤖 (robot comment on behalf of @pauldambra)

Closing this PR. Network request timing should follow the OpenTelemetry HTTP client semantic conventions (http.client.request.duration, unit s, standard attributes). It should not use names that this spec leaves undefined. This also needs a change to the base Metrics spec (#30), because its fixed buckets do not work with durations in seconds.