You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by "Susan L. Cline (JIRA)" <ji...@apache.org> on 2016/06/07 23:13:21 UTC
[jira] [Closed] (QUARKS-33) Changing the metrics selector from a
metric with multiple oplets to a few counters resulted in a bad y-axis
legend
[ https://issues.apache.org/jira/browse/QUARKS-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Susan L. Cline closed QUARKS-33.
--------------------------------
> Changing the metrics selector from a metric with multiple oplets to a few counters resulted in a bad y-axis legend
> ------------------------------------------------------------------------------------------------------------------
>
> Key: QUARKS-33
> URL: https://issues.apache.org/jira/browse/QUARKS-33
> Project: Quarks
> Issue Type: Bug
> Components: Console
> Reporter: Susan L. Cline
> Assignee: Susan L. Cline
> Priority: Minor
>
> When a quarks application has metrics and multiple oplets have a counter say, the x-axis tick marks can become illegible. Although eventually when the refresh interval is called again, the tick marks are removed, the tick marks look bad until this refresh occurs.
> I'll fix it so the tick marks only appear after a refresh for metrics whose tick marks will fit in the space provided.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)