DPDK usage discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: rhjafrooz <rhjafrooz@protonmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: DPDK telemetry plugin for Collectd won't show DPDK application metrics
Date: Wed, 10 Jan 2024 09:18:17 +0100	[thread overview]
Message-ID: <CAJFAV8xwQ5r4SxX5cv2NSa1CJ6WWnC6+eKOVBDBCU20Dgv73yA@mail.gmail.com> (raw)
In-Reply-To: <ifikEfkDFz3Q6il9FxC76NA1uyJUnjhD67D76SGWnLFzk0t85RkfRdF2Pqdf8MINqn9LstVUvEzXhvD_H6HuebR1fYMQEv7Dm2ktXyswtwg=@protonmail.com>

Hello,

On Sat, Dec 30, 2023 at 4:12 PM rhjafrooz <rhjafrooz@protonmail.com> wrote:
>
> I want to use collectd's DPDK telemetry plugin for exporting metrics from DPDK application. But it won't work. I had uncommented LoadPlugin dpdk_telemetry, and my Collectd config for dpdk-telemetry is :
>
> <Plugin dpdk_telemetry>
>
>         ClientSocketPath "/var/run/dpdk/rte/mp_socket"
>         DpdkSocketPath "/var/run/dpdk/rte/dpdk_telemetry.v2"
> </Plugin>
>
>
> I expect Collectd to work as before, but when I open Collectd output metrics (port 9103 by default), It won't show anything.
> (NOTE: I'm running all of them on a single virtual machine in a VMware)

I am not familiar with collectd.
You may have some luck asking here about the dpdk plugin.
However, I suggest you turn to the collectd community first to check
that your collectd configuration is valid before looking at help from
the dpdk side.


-- 
David Marchand


      reply	other threads:[~2024-01-10  8:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 15:12 rhjafrooz
2024-01-10  8:18 ` David Marchand [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJFAV8xwQ5r4SxX5cv2NSa1CJ6WWnC6+eKOVBDBCU20Dgv73yA@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=rhjafrooz@protonmail.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).