toolkit/components/telemetry/Processes.yaml
author Sebastian Hengst <archaeopteryx@coole-files.de>
Mon, 22 May 2017 20:41:12 +0200
changeset 360028 ff997cf7f59424cc221a41f357fe811d23db239e
parent 360018 af4327fd49cd93c717328e61caf1af692a0e52a0
child 360079 589fca202ae60ae457d3622b0ab006ae41eb9f85
permissions -rw-r--r--
Backed out changeset af4327fd49cd (bug 1361661) for bustage in TelemetryProcessData.h. r=backout

# This lists the known child processes we collect Telemetry for.
# The entries are keyed with the names used in Telemetry internally, the same name that is used
# in the main pings payload, i.e. "payload/processes/<process name>". See:
# https://gecko.readthedocs.io/en/latest/toolkit/components/telemetry/telemetry/data/main-ping.html#processes
#
# For now this is only used to inform the data pipeline about new processes, but will be used to
# generate headers with C++ data later (enums, strings, ...).
parent:
  description: This is the main process. It is also known as the parent or chrome process.
content:
  description: This is for processes web content is rendered in.
extension:
  description: >
    This is the WebExtension process. It is a re-used content process, with the data submitted
    separately to avoid skewing other content process Telemetry.
gpu:
  description: This is the compositor or GPU process.