Re: [PATCH v2] usertools: add telemetry exporter

On Tue, Apr 16, 2024 at 3:47 PM Robin Jarry wrote: > > For now the telemetry socket is local to the machine running a DPDK > application. Also, there is no official "schema" for the exposed > metrics. Add a framework and a script to collect and expose these > metrics to telemetry and observability

Re: [PATCH v2] usertools: add telemetry exporter

Hi Robin, I've tested your patch and this is all good for me. The errors are better handled. The most common one is when the socket telemetry is closed and you get: 2024-04-19 15:22:00 ERROR 192.168.122.116 GET /metrics HTTP/1.1: telemetry socket not available Traceback (most recent call las

[PATCH v2] usertools: add telemetry exporter

For now the telemetry socket is local to the machine running a DPDK application. Also, there is no official "schema" for the exposed metrics. Add a framework and a script to collect and expose these metrics to telemetry and observability agree gators such as Prometheus, Carbon or Influxdb. The expo