ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aravindan Vijayan (JIRA)" <>
Subject [jira] [Commented] (AMBARI-18185) Selecting one host when topN is set, throws an error
Date Wed, 17 Aug 2016 18:45:20 GMT


Aravindan Vijayan commented on AMBARI-18185:

On Grafana TopN dashboards, if the user selects just one host, it fails with error.

We have complex conditions for identifying if a top N request is a request for Top N hosts
or Top N metrics. This specific case of 1 Metric & 1 Host (with no wildcards), both conditions
return true, which breaks the downstream flow.

Ideally, only condition should be true at an instance. If both are true, we should reject
the request.

> Selecting one host when topN is set, throws an error
> ----------------------------------------------------
>                 Key: AMBARI-18185
>                 URL:
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-metrics
>    Affects Versions: 2.4.0
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>             Fix For: 2.5.0
>         Attachments: AMBARI-18185.patch
> topN is available by default on almost all Grafana templatized dashboards.
> When viewing any of these dashboards, if only one "host" or templated option is chosen,
then AMS returns with an exception (screenshot attached).
> Sample query:
> collectorhost:6188/ws/v1/timeline/metrics?metricNames=cpu_system._avg&hostname=hostname&appId=HOST&startTime=1470925360&endTime=1470946960&topN=20&topNFunction=avg&isBottomN=false

This message was sent by Atlassian JIRA

View raw message