edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (QUARKS-188) Console metric propagation shouldn't traverse non-injected metric ops
Date Fri, 27 May 2016 12:40:13 GMT

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

ASF GitHub Bot commented on QUARKS-188:
---------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/incubator-quarks/pull/124


> Console metric propagation shouldn't traverse non-injected metric ops
> ---------------------------------------------------------------------
>
>                 Key: QUARKS-188
>                 URL: https://issues.apache.org/jira/browse/QUARKS-188
>             Project: Quarks
>          Issue Type: Task
>          Components: Console
>            Reporter: Dale LaBossiere
>            Assignee: Dale LaBossiere
>            Priority: Minor
>
> QUARKS-22 / PR-116 added "metric propagation" so edge segments get proper width rendering
and edge hovers report metrics across injected ops.
> The traversal code was including (non-injected) CounterOp and RateMetric oplets which
is undesirable since each such oplet is included in the retrieved "counter metrics" hence
each already ended up setting its adjecent edges' metric value.  Hence traversing them too
is unnecessary / extra work.



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

Mime
View raw message