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

PagerDuty(https://www.pagerduty.com/) is widely used for on-call globally. We are welcome the contributions to support it as alarm notification channel.

Kibana version:
7.15

Original install method (e.g. download page, yum, from source, etc.):
staging

Description of the problem including expected versus actual behavior:

The action menu for an integration policy says "Upgrade package policy". It should say "Upgrade integration policy". That's because we only expose the integration concept to users. Packages are an internal co

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

We support opentelemetry, so it should be possible to instrument ruby applications and visualise data on SigNoz. But we don't have lots of expertise in Ruby in the core team, so we have not tested this.

https://github.com/open-telemetry/opentelemetry-ruby

It would be good first issue for folks expert in Ruby to test this and report their findings. If this works fine, we can add this to our d

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:

please look at images

like this