From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id CE1D2A0524; Wed, 5 May 2021 13:26:56 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 4D54B40040; Wed, 5 May 2021 13:26:56 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id CCAFC4003C for ; Wed, 5 May 2021 13:26:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1620214014; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=3snh26gjjCPEEYaNWdDlKsUMJQHvLd9U5eM9N/RSDaU=; b=Z1lLpKUrZ0NNPU/H6th0iwCibFnxyih80tf759qjoBkXM7736kpiHb15ArE/jyXr3fxxQI sjGUTOexzoGUvniF/VBna1aG4jL3GthzQ6HD8DvkJaThzkUcpnGoNVDIVpouwgINIjkVQ3 aagBvQFumL6+KdbJz9wvvGUHV3pT7g0= Received: from mail-vs1-f69.google.com (mail-vs1-f69.google.com [209.85.217.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-592-4Pks2mnHMI2UZEfLYPSyuA-1; Wed, 05 May 2021 07:26:50 -0400 X-MC-Unique: 4Pks2mnHMI2UZEfLYPSyuA-1 Received: by mail-vs1-f69.google.com with SMTP id z21-20020a67d2950000b02902271a3918c4so887885vsi.20 for ; Wed, 05 May 2021 04:26:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3snh26gjjCPEEYaNWdDlKsUMJQHvLd9U5eM9N/RSDaU=; b=WHUTkgXFfXxx2lSnN3GwVY7FxAUgtWyQ8Ww0DBNeVDy4khvhIgoDaPSWIndVcxBphA 0+q/VZ7UGSpm10XnMHYgcjAyZSLUzL/VLogTZkZqu5nZPVO7SNIpfwagtl2MmORe4ny+ P5GgFKGZ0/xHsZFIV+kvtqGHH9/cIN7l2TlQN1BWyTe6qndc0jkPVVLAJoIETnBV9lPQ mwk1Znygs8U4XLSUR5eIWDteUG4bR9yqedPFxhdSi2BcgpvkNPKQNaTQSEyU6kCrPLNy zyP7dAks0vzmrGzF3/A4cIdMy6UxQr+PxLjbDiPrBRG1gCtntn6aAqmIZGVW3wNiVTlz j/9Q== X-Gm-Message-State: AOAM533xQ7CB5PQjlJyRQ1VENs4LD95h/hv4u+Tzdzr3YEbj0hVnWh3y s7TV9j64/ZpWJ9WBJWW2PxgSpbUd89QNkomgo9T3pU2pRG4q+nmHAqVO23WXtR+dSiFmpHwqo4H X00J6t/CClo+YDE0pQtE= X-Received: by 2002:a05:6102:127b:: with SMTP id q27mr25814895vsg.27.1620214010209; Wed, 05 May 2021 04:26:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyR++x8Qny/YGrpMgyMWCfr0mZOXtFRT/HJwvdfN7UnVYR41AaDIan3jAvqIhhnb+hmqCViCCSVs1Ppq4uLJL0= X-Received: by 2002:a05:6102:127b:: with SMTP id q27mr25814889vsg.27.1620214010026; Wed, 05 May 2021 04:26:50 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Wed, 5 May 2021 13:26:37 +0200 Message-ID: To: Harman Kalra Cc: "bruce.richardson@intel.com" , "kevin.laatz@intel.com" , "thomas@monjalon.net" , "stephen@networkplumber.org" , "dev@dpdk.org" , Luca Boccassi , Jerin Jacob Kollanukkaran Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=dmarchan@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] [EXT] Re: DPDK Telemetry library enhancement X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 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 Wed, May 5, 2021 at 12:06 PM Harman Kalra 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