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

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• [ x ] Requirement

Question

• java agent support dubbo 3.0

Above the fields list and in the layer pane, change Change index pattern to Index pattern.

Above fields list:

In layer pane:
![Screen Shot 2021-07-15 at 3 23 11 PM](https://user-images.githubusercontent.com/38990715/125852638-d794c03c-86b1-4

We see many devs from Germany are using SigNoz. It would be be good if README is translated to German.

This will make it easier for devs from Germany and German speaking countries to get started with SigNoz.

Summary

Go 1.16 was released in February and the feature we're most excited about is go:embed. Relevant articles:

• https://golangtutorial.dev/tips/embed-files-in-go/
• https://golang.org/doc/go1.16
• https://golang.org/pkg/embed/

Currently we use pkger to embed web app assets into the binary. This is only enabled in production builds.

Objective

Switch from pkger to

In development, when adding/removing/updating validations there is a redundancy that makes dev a little bit harder some time: the usage of two different ids for the same validation. Here one example of the two ids for one validation:

https://github.com/kiali/kiali/blob/dae08cbfed82b4766115b5b3ea93432ae4071c9b/models/istio_validation.go#L226-L241

The first key is the ide for the associative m

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: