You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@helix.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/06/16 23:37:05 UTC

[jira] [Commented] (HELIX-622) Add new resource configuration option to allow resource to disable emmiting monitoring bean.

    [ https://issues.apache.org/jira/browse/HELIX-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334972#comment-15334972 ] 

ASF GitHub Bot commented on HELIX-622:
--------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/helix/pull/41


> Add new resource configuration option to allow resource to disable emmiting monitoring bean.
> --------------------------------------------------------------------------------------------
>
>                 Key: HELIX-622
>                 URL: https://issues.apache.org/jira/browse/HELIX-622
>             Project: Apache Helix
>          Issue Type: Bug
>            Reporter: Lei Xia
>            Assignee: Lei Xia
>
> Helix creates a set of metrics for each resource. Since job is treated as a regular resource by Helix, each job will emit a set of new metrics to ingraph.  But these metrics are dynamic date metrics, most of them are empty, it is meaningless to put any alerts on them, they are barely used in practice. 
> On the other hand, however, we still need some stable metrics (fix set of metric names) for operational team to monitor the queue and job running status.
> For short term solution, we can add an option in JobConfig to enable emitting a metric for this job, by default, this is disabled.  As a next step, we will need to add a new set of metrics for jobs and workflows.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)