Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
Date: Tue, 7 Feb 2017 04:19:41 +0000 (UTC)
From: "Julia (JIRA)" <jira@apache.org>
To: dev@reef.apache.org
Message-ID: <JIRA.13039685.1486001262000.12493.1486441181642@Atlassian.JIRA>
In-Reply-To: <JIRA.13039685.1486001262000@Atlassian.JIRA>
References: <JIRA.13039685.1486001262000@Atlassian.JIRA> <JIRA.13039685.1486001262410@jira-lw-us.apache.org>
Subject: [jira] [Updated] (REEF-1732) Build Metrics System
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 07 Feb 2017 04:19:46 -0000


     [ https://issues.apache.org/jira/browse/REEF-1732?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julia updated REEF-1732:
------------------------
    Summary: Build Metrics System  (was: Build IMRU Metrics System)

> 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
>         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
(v6.3.15#6346)