Closed
Bug 2077137
Opened 1 month ago
Closed 3 days ago
Attach `flows` metadata to recorded events
Categories
(Data Platform and Tools :: Glean: SDK, enhancement, P1)
Data Platform and Tools
Glean: SDK
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: travis_, Assigned: travis_)
References
(Blocks 1 open bug)
Details
Given the set of active flow instances, add a flows entry to each recorded event for every active flow the event belongs to. Depends on Bug 2077136 for the index. Opening and closing instances is the lifecycle bug. This bug only reads the active set, so tests can seed it directly.
- Add
flowstoRecordedEvent, serialized next tosessionand omitted when empty. Each entry is{ name, seq }, matching the pipeline schema. - In
EventMetric::record_sync, aftershould_record(), do one index lookup onbase_identifier()that returns membership and both boundary roles, so the lifecycle bug can reuse it. - Entries are in alphabetical order by flow name, which the index already provides.
- Membership is not added to
CommonMetricDataor compiled into generated metric code. - Expose
flowsthroughtestGetValuein every binding, since that is the only way to test membership from product code.
| Assignee | ||
Updated•17 days ago
|
Assignee: nobody → tlong
Priority: P3 → P1
| Assignee | ||
Updated•17 days ago
|
Status: NEW → ASSIGNED
| Assignee | ||
Updated•3 days ago
|
Status: ASSIGNED → RESOLVED
Closed: 3 days ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•