gecko-dev/toolkit/components/telemetry/Processes.yaml

27 строки
1.3 KiB
YAML

# 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://firefox-source-docs.mozilla.org/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:
gecko_enum: GeckoProcessType_Default
description: This is the main process. It is also known as the parent or chrome process.
content:
gecko_enum: GeckoProcessType_Content
description: This is for processes web content is rendered in.
extension:
gecko_enum: GeckoProcessType_Content
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:
gecko_enum: GeckoProcessType_GPU
description: This is the compositor or GPU process.
dynamic:
gecko_enum: GeckoProcessType_Default
description: >
This is not a real process, it is used to logically group add-on probes.
It contains data of any probes registered at runtime by add-ons.