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

Hi @apache/skywalking-committers and contributors

SkyWalking INFRA e2e subproject is almost ready to release because this is for testing scope only, we could adopt it in the main repo based on commit IDs.

We are welcome everyone to join this and replace the existing Java Maven based e2e tests. The latest one should be much more friendly and m

Kibana version: 7.14.0

Browser version: Chrome latest

Browser OS version: OS X

Describe the bug: Can we either display a tooltip or remove the "include related objects" option from the copy saved objects between spaces UI. Its permanently checked and greyed out now and that's confusing as an user.

<img width="1792" alt="Screen Shot 2021-07-27 at 5 59 35 PM" src="http

We should create a sample app in django framework and show developers can instrument them and visualise on SigNoz UI. Similar to what we have done for Flask app here - https://github.com/SigNoz/sample-flask-app

This should ideally be a new repo in this org in my opinion

When looking at flamegraphs like this one:

Its not very useful to see this portion of the function name. It would be more convenient if there were some kind of ability to cont

Kiali uses tooltip in multiple locations, in some cases style difers even for the same concepts.

I noticed some changes on this kiali/kiali-ui#1884 but it would require some global issue to review all tooltips and check that they look like similar (at least for the same concept).

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: