1 # This Source Code Form is subject to the terms of the Mozilla Public
2 # License, v. 2.0. If a copy of the MPL was not distributed with this
3 # file, You can obtain one at http://mozilla.org/MPL/2.0/.
5 # Adding a new metric? We have docs for that!
6 # https://firefox-source-docs.mozilla.org/toolkit/components/glean/user/new_definitions_file.html
9 $schema: moz://mozilla.org/schemas/glean/metrics/2-0-0
11 - 'Core :: Storage: Quota Manager'
17 An event recorded on an error of the quota manager or its clients.
18 Since errors are usually propagated up the call chain, all such
19 propagation steps are recorded for an error. This is only active
20 during specific contexts, in particular during storage
21 initialization. No dynamic data is included in the event beyond the
22 error code which will be added through Bug 1670555.
23 This event was generated to correspond to the Legacy Telemetry event
24 dom.quota.try.error#step.
26 - https://bugzil.la/1665088
28 - https://bugzil.la/1665088
31 - storage-telemetry@mozilla.com
36 The context in which the error occurred, e.g. during a storage initialization.
37 Telemetry events are only emitted for selected contexts.
41 Optionally, the frame within stack_id.
45 Optionally, the process in which the error occured.
49 Optionally, the name of the error that occurred.
57 One of WARNING or ERROR.
61 The name of the source code file where the error occurred.
65 The line within source_file where the error occurred.
69 Optionally, the stack within process_id.
71 telemetry_mirror: DomQuotaTry_Error_Step
72 quotamanager.initialize.repository:
74 type: labeled_custom_distribution
76 This metric logs the count of directory entries iterated within the
77 QuotaManager::InitializeRepository function for each repository type.
78 Each instance of this metric is labeled with one of three repository
79 types: "persistent", "temporary" or "default" (there's also "private"
80 repository but that should never be iterated by the function).
81 The main purpose is to track and analyze iteration counts during the
82 initialization process of each repository type, helping to identify
83 performance trends or potential inefficiencies across these repositories.
84 This can provide insight into the impacts of specific code changes,
85 including potential optimizations or regressions.
89 histogram_type: exponential
92 - https://bugzilla.mozilla.org/show_bug.cgi?id=1927260
94 - https://bugzilla.mozilla.org/show_bug.cgi?id=1927260
99 - storage-telemetry@mozilla.com