bug 1495620 - Even dynamic events are no longer sent in 'main' pings r=Dexter
authorChris H-C <chutten@mozilla.com>
Mon, 08 Oct 2018 07:48:35 +0000
changeset 488727 bffefd408262494b20da159ba013f64321254beb
parent 488655 8ab15bf1e8cd11a1f043100d2ef3c51d8ba9aaf6
child 488728 dd0480856174ebb56abe03c063f4833f8c4f5d43
push id246
push userfmarier@mozilla.com
push dateSat, 13 Oct 2018 00:15:40 +0000
reviewersDexter
bugs1495620
milestone64.0a1
bug 1495620 - Even dynamic events are no longer sent in 'main' pings r=Dexter Update documentation to reflect that dynamic events are no longer sent in 'main' pings. Differential Revision: https://phabricator.services.mozilla.com/D7907
toolkit/components/telemetry/docs/collection/events.rst
--- a/toolkit/components/telemetry/docs/collection/events.rst
+++ b/toolkit/components/telemetry/docs/collection/events.rst
@@ -217,17 +217,17 @@ Register new events from add-ons.
   * ``extra_keys`` - *(optional, list of strings)* The valid extra keys for the event.
   * ``record_on_release`` - *(optional, bool)*
   * ``expired`` - *(optional, bool)* Whether this event entry is expired. This allows recording it without error, but it will be discarded. Defaults to false.
 
 For events recorded from add-ons, registration happens at runtime. Any new events must first be registered through this function before they can be recorded.
 The registered categories will automatically be enabled for recording.
 If a dynamic event uses the same category as a static event, the category will also be enabled upon registration.
 
-After registration, the events can be recorded through the ``recordEvent()`` function. They will be submitted in the main pings payload under ``processes.dynamic.events``.
+After registration, the events can be recorded through the ``recordEvent()`` function. They will be submitted in event pings like static events are, under the ``dynamic`` process.
 
 New events registered here are subject to the same limitations as the ones registered through ``Events.yaml``, although the naming was in parts updated to recent policy changes.
 
 When add-ons are updated, they may re-register all of their events. In that case, any changes to events that are already registered are ignored. The only exception is expiry; an event that is re-registered with ``expired: true`` will not be recorded anymore.
 
 Example:
 
 .. code-block:: js