You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Navina Ramesh (JIRA)" <ji...@apache.org> on 2017/05/10 00:35:04 UTC
[jira] [Updated] (SAMZA-1270) Pull out MetricsReporter lifecycle
from Container
[ https://issues.apache.org/jira/browse/SAMZA-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Navina Ramesh updated SAMZA-1270:
---------------------------------
Fix Version/s: 0.14.0
> Pull out MetricsReporter lifecycle from Container
> -------------------------------------------------
>
> Key: SAMZA-1270
> URL: https://issues.apache.org/jira/browse/SAMZA-1270
> Project: Samza
> Issue Type: Improvement
> Reporter: Navina Ramesh
> Assignee: Navina Ramesh
> Fix For: 0.14.0
>
>
> Currently, the lifecycle of many components, including the {{MetricsReporter}} is tied to the container lifecycle. Due to this, StreamProcessor/JobCoordinator will need to manage their own metrics registry and reporters.
> In order to unify the stack, the ideal place for metricsReporter lifecycle will be in the user-facing apis - LocalContainerRunner & LocalApplicationRunner. Every component will simply register its metrics to the reporter dynamically. Iiuc, the {{MetricsReporter}} can implement a {{ReadableMetricsRegistryListener}} interface to register metrics dynamically.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)