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 AD847A0524; Wed, 5 May 2021 10:57:56 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2826A40040; Wed, 5 May 2021 10:57:56 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by mails.dpdk.org (Postfix) with ESMTP id 917FA4003C for ; Wed, 5 May 2021 10:57:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1620205073; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Uti/DmzUto/D2115CSdGMViNPcYnBlhLa5cKfyc8IN8=; b=LLz80vGpB9f08hzIl/vGNvY9r7vkozvwUha4BsuDwKP0UHycrrO7ebC2LhnJQgl2coM1Cb L+2zJt0wlktA46hNSQ6qOr17gSd7L0E0gi8BgAQBy7pfFo033pRHlJDrd69BETK4RRZmZT rZxkZCWM8ba11A/KbBCD/wDeCDZUl84= Received: from mail-vs1-f71.google.com (mail-vs1-f71.google.com [209.85.217.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-53-1_ZLsVlVMfSKDF3fjfB96A-1; Wed, 05 May 2021 04:57:50 -0400 X-MC-Unique: 1_ZLsVlVMfSKDF3fjfB96A-1 Received: by mail-vs1-f71.google.com with SMTP id h1-20020a67b7010000b02902085e833adeso745306vsf.11 for ; Wed, 05 May 2021 01:57:49 -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:content-transfer-encoding; bh=Uti/DmzUto/D2115CSdGMViNPcYnBlhLa5cKfyc8IN8=; b=d76JP1VcoXC+9+VNopB3qCagx4IV9sel1nfHxrLynuEx0qjfdV7M7Lay6KoI3NaHvl hWqDlsFG/em7LX8z2aJG+zRvJRNpow7lIzjWQv7hdzbHApSDzaTYb7stmrPcW1Pu1ouC Z4YAF9j0UXK7ikAkn8LyWPAK/+cAynWzvn1EoWDiwOEODqtTV4quq0amxvgcjFO4n3Yy A4IHxbWRN7b7IV71TqJu2txlotS5hWTtCpFl58a8jPgqQ3Z3CaWaKrc2mGpbWhWt58Mz ZRY4ghdhJNyE6XxANrJ2rpiU2trfJFNJATSuyho7WGX3lbOFIZ5VF3+KwFNxltpxgC7q 3YbA== X-Gm-Message-State: AOAM53272XCNHLwODNaK0BsF8DgKl8HEGKC9EvahpzD/bpSrxjxVehGn N5io66BbnhpevAFu+GzjlHb2pUSAx1u/EZY0vs4EEVYPDgG8ujQetl4gy6iAKGSSDFmaH6n+S1N fBbM+jj/apigus20mKy8= X-Received: by 2002:a67:6b41:: with SMTP id g62mr6545479vsc.5.1620205069498; Wed, 05 May 2021 01:57:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzjl0dvzR8OxaB91lTRbSCgUWFX/MJpVQcGtnujieB6XovPvrgX2dhPsLkPl47Sl5eU+RBU7QY+/IcP2dcHvMQ= X-Received: by 2002:a67:6b41:: with SMTP id g62mr6545469vsc.5.1620205069288; Wed, 05 May 2021 01:57:49 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: David Marchand Date: Wed, 5 May 2021 10:57: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" Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] 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 9:49 AM Harman Kalra wrote: > We have a use case where we need to gather statistics over network. Curre= nt implementation of telemetry library is based on Unix socket, we would li= ke to enhance the scope of library to use network sockets. We understand se= curity challenges with network sockets, to overcome them can we can think o= f two steps: > 1. By default library will be using Unix sockets, it will be user decisio= n to run library with network sockets by passing respective eal flags. > 2. We can introduce some key/password authentication mechanism to the lib= rary, where only authorized clients can get connected to the server. Passwo= rd can be passed by the user as eal flags, something similar to vf token wh= ich 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. > > One more query, can we register driver specific telemetry commands to col= lect driver stats? Is this upstream able? I don't remember a limitation/guideline on this subject. Any command can be registered, this is up to the telemetry client to invoke= it. --=20 David Marchand