2022-08-16 19:08 (UTC-0700), Stephen Hemminger: > Not sure if turning telemetry into a do all control api makes sense.
I'm sure it doesn't, for "do all". Controlling diagnostic collection and output, however, is directly related to the telemetry purpose. > This seems like a different API. > Also, the default would have to be disabled for application safety reasons. This feature would be for collecting additional info in case the collection was not planned and a restart is not desired. If it is disabled by default, it is likely to be off when it's needed. Let's consider how exactly can safety be compromised. 1. Securing telemetry socket access is out of scope for DPDK, that is, any successful access is considered trusted. 2. Even read-only telemetry still comes at cost, for example, memory telemetry takes a global lock that blocks all allocations, so affecting the app performance is already possible. 3. Important logs and traces enabled at startup may be disabled dynamically. If it's an issue, the API can refuse to disable them. 4. Bogus logs may flood the output and slow down the app. Bogus traces can exhaust disk space. Logs should be monitored automatically, so flooding is just an annoyance. Disk space can have a quota. Since the user is trusted (item 1), even if they do it by mistake, they can quickly correct themselves using the same API.
