Drill down in infux 2.0 frontend

__Proposal:__
Is it possible to do drill down using influx 2.0 frontend or dashboard?

What I mean by drill down?
I will give an example to explain what I mean by drill downing in influx 2.0 / chronograf. Assume a 20 students record with columns as :
=> name || pass/fail status || branch || department… etc.

Now I click on any one student present in table under ‘name’ column, dashboard should take me to another table which has more details related to that student, say columns of other table are as :
=> name || total subjects || subject failed || subject passed etc.

Now If i click on any field_value under total subjects column it takes me to another table, say with columns as:
=> name || subject_1 marks || subject2_marks || subject3_marks,…

__Current behavior:__
You run a query and you see the respective values in the columns (assuming you are visualising it as table)

__Desired behavior:__
Want to drill down more such that I can dig in further into that table, such that I click on one field (it acts as hyperlink to a query and takes to new table), it runs a query associated to that field and shows me a new table giving more details about the fields (details can be customised based on the query passed by the user). And keep on drilling down, basically zooming into tables to find more and more details.

__Alternatives considered:__
Describe other solutions or features you considered.

__Use case:__
You have type of sensors collecting various data. Now click on one sensor say weather station. A new table will open and will show all the weather stations and their location. Click on any weather station you can see all the sensors collecting what type of data in the table. Further you can go and see details about particular sensor.

It will give a structured visualisation of the data making it easy for the user to understand it and maintain it.

The issue mentions the InfluxDB 2.0 frontend and dashboards but names no files, tests, or entry points. First clarify the interaction and query configuration requirements, then locate the relevant dashboard UI; done means users can select table values to open successive, configurable detail views.

Written by the indexing model from the issue text.