From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6CAD8A0565; Mon, 23 Mar 2020 12:31:51 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 78EE21C044; Mon, 23 Mar 2020 12:31:50 +0100 (CET) Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 900A41C02D for ; Mon, 23 Mar 2020 12:31:48 +0100 (CET) IronPort-SDR: 0TcTdU1Z35mqZuofQnutbNYCX2h09xnwn4iE56dbcmJnr9sjpzIuEgrcQBNTnZkTGHfr5GSpW+ eXsSe5RSosiw== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Mar 2020 04:31:47 -0700 IronPort-SDR: g48MvS+eQEQ4185rVJRGbMWIpXyKeU42PkoW7l854C9zGDMHQDuNBO3JX5YdO4CgjaL5dewOA0 YUG+RjL277Cg== X-IronPort-AV: E=Sophos;i="5.72,296,1580803200"; d="scan'208";a="447363025" Received: from bricha3-mobl.ger.corp.intel.com ([10.214.201.116]) by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 23 Mar 2020 04:31:46 -0700 Date: Mon, 23 Mar 2020 11:31:41 +0000 From: Bruce Richardson To: Adel Belkhiri Cc: dev@dpdk.org Message-ID: <20200323113141.GA1513@bricha3-MOBL.ger.corp.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dpdk-dev] Exporting DPDK network interfaces statistics X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Sat, Mar 21, 2020 at 02:47:22PM -0400, Adel Belkhiri wrote: > Hello guys, > > I'm trying to develop a monitoring tool capable of exporting some > statistics about DPDK network interfaces. The problem with spawning a > "secondary process", the way proc-info does, is that not all the network > interfaces are "seen" but just those managed by a single primary process. > > I was wondering if there is another way to implement this without spawning > many processes. > > Thank you. > Have you looked into the telemetry library and it's socket interface for getting stats? If you run e.g. testpmd with --telemetry you can view stats using the dpdk-telemetry-client.py script in usertools. There is also some enhancments to telemetry proposed, which might be of interest to you too, since it allows easier querying of the stats: http://patches.dpdk.org/project/dpdk/list/?series=8987