Bug 1851725

Summary: [RFE] Add tags to grafana dashboards
Product: [oVirt] ovirt-engine-dwh Reporter: Aviv Litman <alitman>
Component: GrafanaAssignee: Aviv Litman <alitman>
Status: CLOSED CURRENTRELEASE QA Contact: Ivana Saranova <isaranov>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4.1CC: bugs, emarcus, mperina, pelauter, sradco
Target Milestone: ovirt-4.4.4Keywords: FutureFeature
Target Release: 4.4.4.1Flags: pm-rhel: ovirt-4.4+
pelauter: planning_ack+
sbonazzo: devel_ack+
lleistne: testing_ack+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-engine-dwh-4.4.4.1 Doc Type: Enhancement
Doc Text:
Feature: Add tags to grafana dashboards. The tags are: 1. Cluster 2. DC (Data Center) 3. Host 4. VM 5. SD (Storage Domains) 6. CPU 7. Memory 8. Disk 9. Interface 10. Downtime 11. Uptime 12. OS (Operating System) 13. HA (High Availability) Reason: Adding tags will make it easier to sort and know the contents of dashboards. Result: Each dashboard will have a number of tags that describe the content displayed within it.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-12-21 12:36:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Metrics RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Aviv Litman 2020-06-28 12:10:50 UTC
Description of problem:

We want to add tags to each dashboard (each page) in all oVirt Grafana Dashboards. 
The tags Will include keywords related to the content being displayed.

Comment 4 Ivana Saranova 2020-12-09 14:18:13 UTC
Steps:
1) Login to the Monitoring portal
2) Check that all the dashboards have appropriate tags and filtering by tags is possible

Results:
All of the dashboards have appropriate tags and filtering by tags is possible.

Verified in:
ovirt-engine-4.4.4.3-0.5.el8ev.noarch
ovirt-engine-dwh-4.4.4.2-1.el8ev.noarch

Comment 5 Sandro Bonazzola 2020-12-21 12:36:50 UTC
This bugzilla is included in oVirt 4.4.4 release, published on December 21st 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.4 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.