Merge Timeseries schema#418
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5914e67677
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| { | ||
| "title": "RumTimeseriesEvent", | ||
| "oneOf": [ |
There was a problem hiding this comment.
Add timeseries to the aggregate RUM schema
This block only registers the new event in the mobile schema, but schemas/rum-events-schema.json remains unchanged while scripts/generate.mjs:15 uses that aggregate schema to generate the exported RumEvent types. When consumers validate or generate from the aggregate schema, these mobile timeseries payloads are still rejected and omitted from the package types even though they are now valid mobile RUM events; add the same timeseries branch there and regenerate the definitions.
Useful? React with 👍 / 👎.
What and why ?
Adds a new timeseries RUM event type to the schema, with two concrete event schemas:
timeseries-cpu-schema.jsonandtimeseries-memory-schema.json, registered inrum-events-mobile-schema.json.This backs the new experimental mobile RUM Timeseries feature: periodic CPU and memory samples collected during a session, batched and flushed as their own event type.