Closed
Bug 1798713
Opened 2 years ago
Closed 2 years ago
Increase Glean Events limits (properties, size)
Categories
(Data Platform and Tools :: Glean: SDK, enhancement, P1)
Data Platform and Tools
Glean: SDK
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mak, Assigned: janerik)
References
Details
Attachments
(2 files)
For the new engagement telemetry in the urlbar, we need larger limits than the current one.
We currently have 11 properties, and the longest property is a CSV string made of result types
. The longest result type we have is 20 bytes, most users will have 10 results, but some may increase that value. Though, we expect results over a certain threshold (let's say 25 results) won't be particularly usable.
Thus, I think meaningful sizes, also to keep into account potential future needs, would be:
- 15 properties
- 500 bytes value length. ideally the worst case scenario would be 25 results * 20 chars + 24 commas, though most users have 10 results and most types are shorter, thus we think most cases will be under 200 bytes, and this is a good enough worst case scenario.
Reporter | ||
Updated•2 years ago
|
Summary: Increase Glen Events limits (properties, size) → Increase Glean Events limits (properties, size)
Assignee | ||
Updated•2 years ago
|
Assignee: nobody → jrediger
Status: NEW → ASSIGNED
Type: defect → enhancement
Priority: -- → P1
Assignee | ||
Comment 1•2 years ago
|
||
Assignee | ||
Comment 2•2 years ago
|
||
Assignee | ||
Comment 3•2 years ago
|
||
Assignee | ||
Comment 4•2 years ago
|
||
badboy merged PR #2255: "Bug 1798713 - Events: Increase event extras limit to 15 and event extra value limit to 500 bytes" in 298108e.
This is going into a release today.
Assignee | ||
Comment 5•2 years ago
|
||
This is in v51.8.0.
bug 1799129 is for landing this in m-c and subsequently in Fenix.
Assignee | ||
Updated•2 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•