From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=google.com (client-ip=2a00:1450:4864:20::12e; helo=mail-lf1-x12e.google.com; envelope-from=rhanley@google.com; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=google.com header.i=@google.com header.a=rsa-sha256 header.s=20161025 header.b=ORBSXsmu; dkim-atps=neutral Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 491y7v22XBzDqvh for ; Wed, 15 Apr 2020 06:41:30 +1000 (AEST) Received: by mail-lf1-x12e.google.com with SMTP id t11so881820lfe.4 for ; Tue, 14 Apr 2020 13:41:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=67Qrs7HqOLr7PxG12ieUTqnENQcK05FxyQM3nVs/3Ac=; b=ORBSXsmuD66k4awVdQ+Hj90mA9wWEw63Ra+3AT0StURyqdRN40qW1y5AN8MKlEPNZf f4300246kY6vy/Bw+BK9LTK0tUTgsvmTu+RRLLXHtiIljpMDmxu2Hffhve3tWyBgkr+j McDIghnWlwfbR9Mf/gBOCs05mUH2P9qgw9JPxSmyjoXGLSxEQPuXhjXAH0Y2GaFZYRKO YEOud+LOlCpy3GghetAEJTV0QR98kKo2g+/uDCN4zGpBvZ21GWme+Beiay2JKDx1vaXu lCde7khVYUSRUXd0eF7QcI0SI+isrBfSV2K9t2Svci59OiPPbSJxu1+/615/Kg6+FLPs Eguw== 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=67Qrs7HqOLr7PxG12ieUTqnENQcK05FxyQM3nVs/3Ac=; b=O/3m6V1vad8kd4ndlmQgS3Sdy/OmAyDV6c6VvPgBpcPm3Dma24IKwbiDwevUzicDr9 Q6QRufV/KtzndDEPKAX6D0JYMGLuVpbp12uIqF2pS34DIX0LCFGyksLfT7j2MtDCM8nz gJPNrZffXd+SrsKSzND9hBHHY0kCfxh6gmACgr+cf+b5ACHICUwUAXTudoY91zvrgWMb 3NzM9drjVnxwtHj7AP+P+LvH2TVekXzKnpvh3nq1taCtBRRPRenh1fXR5ezH/S3tbKtZ GXOsZG0eiUv4WaFd72jyOfmLn2ipdSW/HDV7s0ol+sYIOLyhfnWxrE2Byp6Hi/wHavm6 9Ycg== X-Gm-Message-State: AGi0PuY5ws7otoFODU1vOO5v58wyin6VJc7gNHUTL7WyJfbmyXJzu947 aw8CX60Ltt5HQM377pEpLrB/N1BOnYHTO6zAB7Jhlw== X-Google-Smtp-Source: APiQypKJgsJfqIeSmLZVpgOrwwZz5oGD6HfrPjZHKokR8C32algS5wY5vlA9VO/XY0UgQmNI0blCem3tyAvVnL8uGXg= X-Received: by 2002:ac2:489b:: with SMTP id x27mr972876lfc.60.1586896885940; Tue, 14 Apr 2020 13:41:25 -0700 (PDT) MIME-Version: 1.0 References: <20200410210033.GA9295@mauery.jf.intel.com> <85700953-1CBE-4DFB-9A5B-AF64B9735735@fuzziesquirrel.com> In-Reply-To: From: Richard Hanley Date: Tue, 14 Apr 2020 13:41:14 -0700 Message-ID: Subject: Re: Sensor history To: Vijay Khemka Cc: Brad Bishop , Vernon Mauery , "openbmc@lists.ozlabs.org" Content-Type: multipart/alternative; boundary="0000000000002eef2805a3463970" X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Apr 2020 20:41:32 -0000 --0000000000002eef2805a3463970 Content-Type: text/plain; charset="UTF-8" > Hi Team, > > There is a telemetry proposal in docs and repository. > https://github.com/openbmc/docs/blob/master/designs/telemetry.md > https://github.com/openbmc/telemetry > The proposal seems promising and complete. > What is the implementation status? I'm also curious about a status update here. Were there any design issues that needed to be worked out, or is it ready to develop? >> To implement the Redfish Telemetry service would we need to store them on >> the BMC as well? >It will be nice if we can store it in RAM at least with larger data and some diskspace >With small log rotate. The Telemetry Service already has a concept of log rotation, but overall I agree that storing in RAM first with optional persistence is better than the other way around. - Richard --0000000000002eef2805a3463970 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> Hi Team,>
> T= here is a telemetry proposal in docs and repository.
>=C2=A0https://github.com/openbmc/docs/blob/mast= er/designs/telemetry.md
>=C2=A0https://github.com/openbmc/= telemetry
= > The proposal seems promising and complete.
> What is the implementation status?
=
I'm also curious about a status update here.=C2=A0 Were = there any design issues that needed to be worked out, or is it ready to dev= elop?

>>=C2=A0 =C2=A0 To implement the Redfish Telemetry service = would we need to store them on=C2=A0
>>=C2=A0 =C2=A0 the BMC as we= ll?
>It will be nice if we can store it in RAM at least with l= arger data and some diskspace
>With small log rotate.
<= br>
The Telemetry Service already has a concept of log rotation, = but overall I agree that storing in RAM first with optional persistence is = better than the other way around.
- Richard
--0000000000002eef2805a3463970--