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)

enhancement

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 flows to RecordedEvent, serialized next to session and omitted when empty. Each entry is { name, seq }, matching the pipeline schema.
  • In EventMetric::record_sync, after should_record(), do one index lookup on base_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 CommonMetricData or compiled into generated metric code.
  • Expose flows through testGetValue in every binding, since that is the only way to test membership from product code.
Assignee: nobody → tlong
Priority: P3 → P1
Status: NEW → ASSIGNED
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.