mycroft-core/mycroft/client
Åke Forslund baa15b98aa Send timing metrics for various subsystems
====  Tech Notes ====
STT, intent handling, intent fallbacks, skill handlers are now timed and
tied together with a ident (consistent through the chain so the flow from
STT until completion of the skill handler can be follewed.

TTS execution time is also measured, right now this is not tied into the
ident due to the nature of the speech.

The report is always called "timing" and always contain the following
fields:

- id: Identifier grouping the metrics into interactions
- system: Which part (STT, intent service, skill handler, etc)
- start_time: timestamp for when the action started
- time: how long it took to execute the action

The different system adds their own specific information, for example
the intent_service adds the intent_type, i.e. which handler was matched.

==== Protocol Notes ====
mycroft.skills.loaded is sent togheter with skill id and skill name
whenever a skill is loaded. This is used in the intent_service to
convert from id to skill name when reporting
2018-01-08 18:01:03 -06:00
..
enclosure Bump the required enclosure version to 1.3.0. This pulls in 2017-12-22 12:32:40 -06:00
speech Send timing metrics for various subsystems 2018-01-08 18:01:03 -06:00
text Python 2/3 compatibility (#1259) 2017-12-18 17:24:21 -06:00
__init__.py Change to Apache 2.0 license from GPLv3.0 2017-10-04 01:28:44 -05:00