You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@edgent.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/03/16 19:24:33 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15197872#comment-15197872 ] 

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

GitHub user home4slc opened a pull request:

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

    [QUARKS-33] fixed x-axis legend when many oplets have metrics

    This is for QUARKS-33, when the metrics graph was in between refreshes if the x-axis tick marks were too numerous after changing the metric type selector it appeared with all the numbers mangled.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/home4slc/incubator-quarks fix_metrics_chart

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-quarks/pull/17.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #17
    
----
commit 9220108b4e25e890ab738cca509625084eae41f8
Author: Susan L. Cline <ho...@apache.org>
Date:   2016-03-16T18:07:16Z

    QUARKS33 fixed x-axis legend when many oplets have metrics

----


> 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)