Open Bug 1345560 Opened 4 years ago Updated 4 years ago

Standardize probe version expiry fields on "expires_after_version"

Categories

(Toolkit :: Telemetry, enhancement, P3)

Product:
Toolkit
Component:
Telemetry
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox55 --- affected

People

(Reporter: gfritzsche, Unassigned)

Details

(Whiteboard: [measurement:client]) 

Due to confusing semantics with the current implementation, we should standardize on something that is more clear.

Currently we use:
- Histograms.json uses "expires_in_version"
- Scalars.yaml uses "expires"
- Events.yaml uses "expiry_version"

We should instead use e.g. "expires_after_version".

This will need some pipeline work first to be unblocked, to pick up the new field name(s).
So, for once and for all, "expires_after_version": "55" means that the probe is valid within 55.* but will stop working in 56?
You need to log in before you can comment on or make changes to this bug.