metrics.yaml (3709B)
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/. 4 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 7 8 --- 9 $schema: moz://mozilla.org/schemas/glean/metrics/2-0-0 10 $tags: 11 - 'Cloud Services :: Firefox: Common' 12 13 uptake.remotecontent.result: 14 uptake_remotesettings: 15 type: event 16 disabled: true # To be controlled by server knobs due to expected high volume 17 description: > 18 Was the remote content successfully pulled? This uptake telemetry 19 allows to monitor the behaviour of our clients when it comes to 20 fetching data from remote servers. This helps defect-detection and 21 allow observation of the proportion of success among clients and 22 sources, the distribution of error causes, and its evolution over 23 time. 24 This event was generated to correspond to the Legacy Telemetry event 25 uptake.remotecontent.result.uptake#remotesettings. 26 bugs: &uptake_remotecontent_result_uptake_bugs 27 - https://bugzil.la/1517469 28 - https://bugzil.la/1617133 29 data_reviews: &uptake_remotecontent_result_uptake_data_reviews 30 - https://bugzil.la/1517469 31 - https://bugzil.la/1617133 32 notification_emails: &uptake_remotecontent_result_uptake_emails 33 - mleplatre@mozilla.com 34 - bens-directs@mozilla.com 35 expires: never 36 extra_keys: &uptake_remotecontent_result_uptake_extra 37 value: 38 description: > 39 The `value` of the event. Mirrors to the Legacy Telemetry 40 event's `value` parameter. 41 type: string 42 source: 43 description: > 44 A label to distinguish what is being pulled or updated in the component (eg. recipe id, settings collection name, ...). 45 46 type: string 47 trigger: 48 description: > 49 A label to distinguish what triggered the polling/fetching of remote content (eg. "broadcast", "timer", "forced", "manual") 50 51 type: string 52 age: 53 description: > 54 The age of pulled data in seconds (ie. difference between publication time and fetch time). 55 56 type: string 57 duration: 58 description: > 59 The duration of the synchronization process in milliseconds. 60 61 type: string 62 timestamp: 63 description: > 64 The current timestamp, received during synchronization. 65 66 type: string 67 errorName: 68 description: > 69 An optional string with the error name attribute in case of failure. 70 71 type: string 72 telemetry_mirror: UptakeRemotecontentResult_Uptake_Remotesettings 73 no_lint: 74 - COMMON_PREFIX 75 76 uptake_normandy: 77 type: event 78 description: > 79 Was the remote content successfully pulled? This uptake telemetry 80 allows to monitor the behaviour of our clients when it comes to 81 fetching data from remote servers. This helps defect-detection and 82 allow observation of the proportion of success among clients and 83 sources, the distribution of error causes, and its evolution over 84 time. 85 This event was generated to correspond to the Legacy Telemetry event 86 uptake.remotecontent.result.uptake#normandy. 87 bugs: *uptake_remotecontent_result_uptake_bugs 88 data_reviews: *uptake_remotecontent_result_uptake_data_reviews 89 notification_emails: *uptake_remotecontent_result_uptake_emails 90 expires: never 91 extra_keys: *uptake_remotecontent_result_uptake_extra 92 telemetry_mirror: UptakeRemotecontentResult_Uptake_Normandy 93 no_lint: 94 - COMMON_PREFIX