observability

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

Question

When viewing storage plugins, I find a relationship between them.
If H2 storage plugin use "order by" in the query statement, InfluxDB plugin will use "top" or "bottom" function in its implement.
But I find a difference of IBrowserLogQueryDAO in storage plugins.

• BrowserLogQuery.java in InfluxDB storage plugin: the query contains a sort function "top".
• H2BrowserLogQue

Since Lens is no longer considered new, change to Lens is the recommended editor for creating visualizations.

<img width="258" alt="Screen Shot 2021-08-18 at 10 12 07 AM" src="https://user-images.githubusercontent.com/3899

What's it about?
When you want to select the drop-down menu box in the console, you can search by regular expression or sort by the letters A-Z
What's the reason why we need it?
Can improve the development efficiency, shorten the search time
I believe this is an important feature for Kubesphere. There're a few use cases:
For example, if I have 200 services on a project, I have to manu

Bug description

Please describe.
If this affects the front-end, screenshots would be of great help.
in the development environment if we make any change. change is not reflected over the browser

Expected behavior

change should be reflected immediately without manually refreshing the page

How to reproduce

you can change any text

Thank you for your bug repor

Sometimes its possible for the sidebar to out of sync with the current route. To reproduce:

1. Select single view
2. Select comparison view
3. Hit "back" button

It would be helpful to add a 'Download' (to file) option to the Kiali Debug information view, instead of having to copy/paste into a file.

Why: When opening the Event Injection modal for a particular eventBus, the tool populates each field (source, detail type, and detail) with the last values used for that eventBus. Allowing all events to be saved, similar to the command history in the terminal, will allow users to quickly test multiple events without having to type the same parameters repeatedly.

Expected Behaviour: