Link added directly to Node/Service page from Query Analytics filters, opens in new window
Description
How to test
How to document
Attachments
- 18 Sep 2020, 02:22 PM
- 18 Sep 2020, 02:11 PM
- 20 Aug 2020, 12:53 PM
Smart Checklist
Activity
Tiago Mota September 22, 2020 at 8:05 AM
Fixed every problem except for the second. We are using service type to identify what dashboard to go, pxc clusters or other mysql clusters have the same service type of mysql so will always jump to that dashboard, even though for standard mysql clusters there will be no data. @Roma Novikov what do you think of this behaviour? Do you know if there's another way to distinguish between clusters besides the service type?
Former user September 18, 2020 at 2:33 PM
Checked with --addclient=mo,1 --mongomagic --with-sharding --addclient=ms,1 --group-replication
remove the icon for n/a items
ms-prod-cluster redirects to PXC/Galera Cluster Summary
rs1 and rs2 redirects to http://3.21.52.169/graph/d/; should be MongoDB ReplSet Summary
mongodb_config2 redirects to http://3.21.52.169/graph/d/mysql-instance-summary/mysql-instance-summary?var-service_name=mongodb_config_2
mongodb_config3 redirects to http://3.21.52.169/graph/d/postgresql-instance-summary/postgresql-instance-summary?var-service_name=mongodb_config_3
Many service names redirect to [http://3.21.52.169/graph/d/undefined-instance-summary/undefined-instance-summary...
|http://3.21.52.169/graph/d/undefined-instance-summary/undefined-instance-summary]
Tiago Mota September 17, 2020 at 1:06 PM
Another workaround, similar to what Nurlan mentioned, was used to do this task without specific backend. Prometheus Datasource was used through grafana variables to get service type for clusters, replication sets and services.
Nurlan Moldomurov September 16, 2020 at 10:04 AM
@Tiago Mota actually there is workaround to figure out what's the cluster type is there.
You can get all services and exporters and check if they have the same cluster that you need and based on service_type or agent_type redirect user to a right page.
The same with replication set.
Roman Misyurin September 9, 2020 at 1:53 PM
We discussed with @Nurlan Moldomurov the possibility of adding additional backend functionality for the https://perconadev.atlassian.net/browse/PMM-6515#icft=PMM-6515. However an interesting problem appeared. For example, links in Cluster set section may lead us to different dashboards, for MySQL and MongoDB. But one cluster set may be related to both database types at the same time so we cannot simply use link to a one specific dashboard
@Nurlan Moldomurov @Alexander Blinkov I guess we need deeper research on a backend side because issue looks not so trivial as it seemed to be
The problem: When the user is working on some investigation in QAN it's very hard to go from QAN to Dashboards to see metrics of some Database Server or node.
Users need to use the PMM menu and go to Overview Dashboard and then to some Summary dashboard. This complicates user flow and our Navigation and dashboards.
Proposed solution: let the user easily go from any QAN page to some specific Single object Dashboards with the appropriate parameters.
For users, this will let go to needed pages faster. for PMM dev team - in future, we can simplify our dashboards
UI: Additional icon with link to the dashboard for object/label
https://www.figma.com/proto/O0NVSULrl5vNHEyVtM0rQE/QAN-Fixes-Ver-1.4?node-id=779%3A2&scaling=min-zoom
Examples:
Node name: server1 => "/graph/d/node-instance-summary/node-summary?....&var-node_name=server1&..."
List of labels -> dashboards :
Cluster -> /graph/d/mongodb-cluster-summary/mongodb-cluster-summary or /graph/d/pxc-cluster-summary/pxc-galera-cluster-summary
Replication Set -> /graph/d/mongodb-replicaset-summary/mongodb-replset-summary or /graph/d/mysql-replicaset-summary/mysql-replication-summary
Node Name -> /graph/d/node-instance-summary/node-summary
Service Name -> /graph/d/postgresql-instance-summary/postgresql-instance-summary or /graph/d/mysql-instance-summary/mysql-instance-summary or /graph/d/mongodb-instance-summary/mongodb-instance-summary
Docs:
1/ Mention the feature in the QAN section
2/ Update the images to visualize the new icon