Overview
| Comment: | added (incomplete) docs/manual/devnotes.txt for telemetry usage |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | v1.65-telemetry |
| Files: | files | file ages | folders |
| SHA1: |
ce9c3e41f2eba4d31eb717c30359efa7 |
| User & Date: | bjbarcla on 2019-02-27 17:17:32 |
| Other Links: | branch diff | manifest | tags |
Context
|
2019-02-27
| ||
| 18:09 | wip check-in: 074c8889ef user: bjbarcla tags: v1.65-telemetry | |
| 17:17 | added (incomplete) docs/manual/devnotes.txt for telemetry usage check-in: ce9c3e41f2 user: bjbarcla tags: v1.65-telemetry | |
| 17:16 | capture telemetry todo check-in: 44acc1ef5a user: bjbarcla tags: v1.65-telemetry | |
Changes
Added docs/manual/devnotes.txt version [e6b6b73f5f].
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 | Developer Notes --------------- Collected here are some topics that may interest the megatest developer. telemetry ~~~~~~~~~ A new feature introduced in v1.6525 allows a centralized debug messaging system. Debugging client-server issues is greatly aided by a centralized, time coherent log of events across test execution, server, and runner. This is provided by the telemetry feature source code call example [source,ini] [telemetry] host <IP where telemetry daemon will run> port <UDP port to listen -- we recommend 5929> want-events <comma separated list of telemetry-log keywords [source,ini] [telemetry] host 10.38.32.91 port 5929 want-events ALL [source,scheme] (common:telemetry-log <keyword string> Usage: 1. Add telemetry section to megatest.config 2. Start telemetry daemon telemetry-daemon -a start -l /tmp/my-telemetry.log 3. Run megatest 4. examine / parse telemetry log |