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 issues.

Apache SkyWalking Component

Java Agent (apache/skywalking-java)

What happened

we config trace ignore paths by "agent/config/pm-trace-ignore-plugin.config", but found paths ends by "/" are not ignored with "**".

example configuration i

Describe the bug:

This is an issue raised on the EUI side: elastic/eui#5327
Safari respects the spec on this and we could fix this on the consumer side providing a step="any" to the EuiFieldNumber components without data bounds.

A non-complete lists of such inputs are:

• color stop UI inputs
• static value input

Some examples of it:
<img width="347" a

What's it about?

When I need to batch stop (scale replicas to 0) workloads, the operation is inconvenient. I suggest adding a stop button here.

/area console
/kind feature-request

Is your feature request related to a problem?

The first step towards app optimization

Please describe.
Configure whyDidYouRender under the development env

**Note: make sure it is compatible with all the custom hooks that we are using in the project **

This idea was previously discussed in slack

Clicking on a table item

Should populate the highlight search

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.

We currently use two separate mechanisms to format numbers with SI units:

• this one in use by the IcicleGraph hover tooltip
• this one in use by the MetricsGraph axis an

The recently added flags in timescale/promscale#578 are yet to be updated in prom-migrator's readme which can be found here.

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: