Closed Bug 1676682 Opened 4 years ago Closed 4 years ago

Should we add "baseline" events to the "metrics" ping?

Categories

(Data Platform and Tools :: Glean: SDK, enhancement)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Dexter, Unassigned)

Details

The "baseline" ping gives a nice, quick signal of a product usage. The "metrics" ping usually contains more data, with a slower latency.

Analysts often require correlating "metrics" and "baseline" pings, to know how much a user was active within a "metrics" ping measurement window.

Pros:

  • Allows "easy" correlation of the "metrics" ping with "baseline" ping events.
  • It's technically very easy to achieve ;-)

Cons:

  • The SDK sends any ping containing events at startup, because we can't guarantee the monotonicity of event timestamps (this will increase the number of "metrics" ping being sent, because we'll send one each time a product using the SDK starts).
  • It would be confusing for data users to understand how events in the "metrics" ping behave: will they show up in the "events_daily" table?

Mike, does this capture what we talked about?

Flags: needinfo?(mdroettboom)

Yes, this captures what we talked about.

For additional context, the proposal regarding connecting metrics and events pings: https://docs.google.com/document/d/164Oo1eRw9FBms9JwKwgrw6u8Q0epHVR-fuUmH5PGmdU/edit?usp=sharing

Flags: needinfo?(mdroettboom)

We now send a foreground_count and also a labeled counter submitted_pings. This should capture some information to combine these pings.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.