On Wed, May 5, 2021 at 9:49 AM Harman Kalra <hka...@marvell.com> wrote: > We have a use case where we need to gather statistics over network. Current > implementation of telemetry library is based on Unix socket, we would like to > enhance the scope of library to use network sockets. We understand security > challenges with network sockets, to overcome them can we can think of two > steps: > 1. By default library will be using Unix sockets, it will be user decision to > run library with network sockets by passing respective eal flags. > 2. We can introduce some key/password authentication mechanism to the > library, where only authorized clients can get connected to the server. > Password can be passed by the user as eal flags, something similar to vf > token which is uuid based. > Kindly provide us suggestions/challenges over this enhancements.
Rather than implement a new protocol, and code a new client, would collectd fulfill your need? Info currently retrieved by the telemetry collecd plugin is hardwired. Maybe some configuration could be added to this plugin for your new stats. > > One more query, can we register driver specific telemetry commands to collect > driver stats? Is this upstream able? I don't remember a limitation/guideline on this subject. Any command can be registered, this is up to the telemetry client to invoke it. -- David Marchand
