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

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

I find some configurations are in configurations.md , but not in the agent.config , such as agent.trace_segment_ref_limit_per_span 、agent.instance_properties[key]=value . Otherwise , the configuration ```

• Rename useUrlParams() to useLegacyUrlParams()
• Rename getApmHref() to getLegacyApmHref

Replaces elastic/kibana#105914

What's it about?
Upgrade Ingress API to networking.k8s.io/v1.

What's the reason why we need it?
Ingress is the core component that is used by the KubeSphere Routes feature. KubeSphere is still using the old api "extensions/v1beta1" both Frontend and Backend. However "extensions/v1beta1" Ingress is deprecated in v1.14+, unavailable in v1.22+. So we need to upgrade it to the latest v

Bug description

Please describe.
If this affects the front-end, screenshots would be of great help.

There are two packages of @babel/core one in dependencies and another one in devDependecies

<img width="1430" alt="Screenshot 202

Pyroscope server should respect request context. If a client cancels a request or it's timed out, any related activity (such as an expensive query) must be cancelled immediately.

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.

Only on first load do we show a loading animation, not on subsequent ones, this should be fixed.

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