You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@eagle.apache.org by "Hao Chen (JIRA)" <ji...@apache.org> on 2016/11/11 06:08:58 UTC

[jira] [Resolved] (EAGLE-654) Fix alert engine open metric system per tuple

     [ https://issues.apache.org/jira/browse/EAGLE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hao Chen resolved EAGLE-654.
----------------------------
    Resolution: Fixed

> Fix alert engine open metric system per tuple
> ---------------------------------------------
>
>                 Key: EAGLE-654
>                 URL: https://issues.apache.org/jira/browse/EAGLE-654
>             Project: Eagle
>          Issue Type: Bug
>    Affects Versions: v0.5.0
>            Reporter: Hao Chen
>            Assignee: Hao Chen
>             Fix For: v0.5.0
>
>
> Currently alert engine open metric system per tuple which will waste connection and throughput:
> https://github.com/apache/incubator-eagle/blob/master/eagle-core/eagle-alert-parent/eagle-alert/alert-engine/src/main/java/org/apache/eagle/alert/engine/runner/AlertBolt.java#L131
> In order to export metric in eagle, app developer (including alert engine) should never touch MetricSystem directly but  should use storm native metric framework to declare and update metric, and eagle framework will automatically receive metrics and export as configured.



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