Bug 1849423 - Update trend dashboard descriptions and indentation
Summary: Update trend dashboard descriptions and indentation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine-dwh
Classification: oVirt
Component: Grafana
Version: 4.4.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.4.1
: 4.4.1.2
Assignee: Shirly Radco
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-21 15:16 UTC by Aviv Litman
Modified: 2020-07-06 06:58 UTC (History)
0 users

Fixed In Version: ovirt-engine-dwh-4.4.1.2
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-07-06 06:58:04 UTC
oVirt Team: Metrics
Embargoed:
pm-rhel: ovirt-4.4?
alitman: planning_ack?
pm-rhel: devel_ack+
alitman: testing_ack?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 109711 0 master MERGED Update trend dashboard indentation and description 2020-07-06 06:57:11 UTC

Description Aviv Litman 2020-06-21 15:16:56 UTC
Description of problem:

We want to add to trend dashboards description, and update the queries indentation and comments. 

In addition we want to fix upper/lower case letters errors in the dashboard and queries.

We also want to make sure we update all queries to use hourly and daily tables

Version-Release number of selected component (if applicable):
4.4.1

How reproducible:
100%

Steps to Reproduce:
1. in grafana go to 'Ovirt Trend Dashboards' folder  

Actual results:

descriptions and comments not always correct or found,
indentation not consistent and clean,
upper/lower case letters inconsistent,
in virtual machines trend dashboard all the reports(BR10A) using only the hourly table.

   
Expected results:

Correct and detailed descriptions and comments,
consistent and clean indentation,
all the queries using hourly and daily tables,
consistent upper/lower case letters in titles, descriptions, and queries


Additional info:


Note You need to log in before you can comment on or make changes to this bug.