Open
Bug 1908397
Opened 1 year ago
Updated 1 year ago
Suggest Metrics (Rust side)
Categories
(Application Services :: Suggest, enhancement, P3)
Application Services
Suggest
Tracking
(Not tracked)
NEW
People
(Reporter: bdk, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [disco-])
Attachments
(1 file)
Split off from https://bugzilla.mozilla.org/show_bug.cgi?id=1901779
Adding metrics is complicated by the fact that we can't call Glean directly, but need to forward the calls through our consumers. However, for queries it's not so hard. We can return a metrics struct alongside the query results, like how SyncManager returns them as part of SyncResult
This issue is for defining metrics in components/suggest/metrics.yaml that we want to track and returning those metrics from our API calls. Out of scope is actually recording those metrics, since that has to happen in the consumer code.
Query metrics:
- Total query time
- Query time for each individual provider
Ingest metrics:
- time to download data (total and also per-provider)
- time to update the database (total and also per-provider)
| Reporter | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Severity: -- → N/A
Priority: -- → P3
| Reporter | ||
Updated•1 year ago
|
Summary: Suggest Query Metrics → Suggest Metrics (the easy part)
| Reporter | ||
Updated•1 year ago
|
Summary: Suggest Metrics (the easy part) → Suggest Metrics (metrics.yaml)
| Reporter | ||
Updated•1 year ago
|
Summary: Suggest Metrics (metrics.yaml) → Suggest Metrics (Rust side)
Comment 2•1 year ago
|
||
You need to log in
before you can comment on or make changes to this bug.
Description
•