On Wed, May 5, 2021 at 12:06 PM 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. > > Thanks David, but our requirement is to get statistics remotely over network. > DPDK process and daemon may not be running on the same platform.
collectd can act as a local agent for the system hosting the dpdk process and forward the retrieved data to another "central" collectd, using the "network" https://collectd.org/wiki/index.php/Networking_introduction With collectd plugins, it also opens the possibility to gather other metrics (out of dpdk) from this system and/or publish in different forms the collected data. -- David Marchand
