From dev-return-16357-archive-asf-public=cust-asf.ponee.io@reef.apache.org Mon May 14 21:09:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 1E116180627 for ; Mon, 14 May 2018 21:09:04 +0200 (CEST) Received: (qmail 92285 invoked by uid 500); 14 May 2018 19:09:04 -0000 Mailing-List: contact dev-help@reef.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@reef.apache.org Delivered-To: mailing list dev@reef.apache.org Received: (qmail 92270 invoked by uid 99); 14 May 2018 19:09:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 May 2018 19:09:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 5085B1806D2 for ; Mon, 14 May 2018 19:09:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id K4mCpglDDX25 for ; Mon, 14 May 2018 19:09:02 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 361475FB2C for ; Mon, 14 May 2018 19:09:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 639B6E0F8D for ; Mon, 14 May 2018 19:09:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id B3AA5217AC for ; Mon, 14 May 2018 19:09:00 +0000 (UTC) Date: Mon, 14 May 2018 19:09:00 +0000 (UTC) From: "Mandy Shieh (JIRA)" To: dev@reef.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (REEF-1732) Build Metrics System MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/REEF-1732?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16474= 662#comment-16474662 ]=20 Mandy Shieh commented on REEF-1732: ----------------------------------- PR that expands and enhances MetricsService available here: https://github.com/apache/reef/pull/1460 > Build Metrics System > -------------------- > > Key: REEF-1732 > URL: https://issues.apache.org/jira/browse/REEF-1732 > Project: REEF > Issue Type: New Feature > Components: IMRU, REEF > Reporter: Julia > Assignee: Julia > Priority: Major > Attachments: IMRU Metrics System.docx > > > IMRU Metrics is to provide metrics data to the system so that it can be s= hown to the user for monitoring or diagnosis. The goal is to build an E2E f= low with simple/basic metrics data. We can then add more data later.=20 > * IMetricsProvider - there are multiple sources of metrics data: > 1.Task metrics. This is in particular for IMRU task such as current ite= ration, progress. Each task can send task state back to driver and let driv= er to aggregate it. Alternatively, as UpdateTask knows current iterations a= nd progress, to start with, we can just get task status from update task. T= he task metrics can be provided by task function like IUpdateFunction and s= end to driver by task host as TaskMessage with heartbeat.=20 > 2. Driver metrics =E2=80=93 For IMRU driver, it can be system state suc= h as WaitingForEvaluator or TasksRunning, current retry number, etc. Those = driver states are maintained inside IMRU driver.=20 > 3. IMRUDriver will implement IMetricsProvider and supply metrics data.= =20 > * IMetricsSink =E2=80=93 the metrics data will be output somewhere so tha= t it can be consumed by a monitoring tool. An interface IMetricsSink will b= e defined to sink metrics data. An implementation of the interface can stor= e the data to a remote storage. Multiple sinks can be injected.=20 > * MetricsManager =E2=80=93 It schedules a timer to get metrics from IMetr= icsProviders and output the metrics data with IMetricsSinks > Attached file shows the diagram of the design.=20 -- This message was sent by Atlassian JIRA (v7.6.3#76005)