1508948 - Implement the "timespan" metric type specific API in glean

Status: RESOLVED FIXED

(Toolkit :: Telemetry, defect, P1)

Description

[Alessio Placitelli [:Dexter]]

This bug is about implementing the "timespan" metric type in glean.

From the SDK spec [1]:

> Timespan
> Can record one timespan measurement.
> 
> Each time a timespan is measured, it is added to this value.  This value is zero'd every time it is sent with a ping.  Therefore, it is possible to use this to measure the total time spent in e.g. a particular function or view, even if that function was called multiple times.
> 
> Additional properties:
> time_unit: (string, required) Specifies the unit that results will be stored and displayed in.  If not provided, it defaults to milliseconds.  Timespans are sent to the backend as integers, so unit also implies the maximum resolution at which timespans are recorded.        Accepted values are: "nanosecond", "microsecond", "millisecond", "second", "minute", "hours", "day".
> 
> Examples:
> Record in ms how long it took to load settings.sqlite from disk.
> 
> Errors:
> invalid_value: If the timer is started before being ended, this is considered an error and reported through the error-reporting mechanism.

Comment 1

[Alessio Placitelli [:Dexter]]

[1] - https://docs.google.com/document/d/186GI_2ljdqWqWTBk5P3QjHD3BwpMyd8kRayRAuz1-dk/edit#

Comment 2

[Alessio Placitelli [:Dexter]]

Attachment: GitHub Pull Request

Comment 3

[Alessio Placitelli [:Dexter]]

The PR was reviewed and merged, finally closing this :)