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.

The broadcast-channel dependency has served as a cross-browser shim to provide support for the BroadcastChannel Web API.

Until now, Safari was the only supported browser without native support for BroadcastChannel. Safari 15.4 now ships with [native support for BroadcastChannel](https://webkit.org/blog/12445/new-webkit

Requirement - what kind of business use case are you trying to solve?

Actual the windows executables (jaeger-agent.exe, jaeger-collector.exe, ...) don't have a version set. It is hard to identify the current used version and check if the actual used version is outdated.

Probl

Add a network option in creating workload

like rancher‘s Networking tab

** During workload creation, user can customize own hosts and DNS search doma

Bug description

Header in Top Endpoint section overflows in browser with reduced width

Expected behavior

Header shouldn't overflow

How to reproduce

1. Go to SigNoz dashboard metrics page with reduced browser window width
2. Open any application
3. Top Endpoint panel header appears overflowing

Version information

• Signoz version: v0.7.1
• *Browser version

Recommend waiting on pyroscope-io/pyroscope#927 before working on this

What happened:
I created a pod with a "com.acme/fooBar" label.
The l

Some pages give React warnings when you visit them and inspect the dev console. This is probably minor but would be good to resolve.

Services page:

Istio Config details page:
![Screenshot from 2022-03-04 12-15-03](https://user-images.githubusercontent

The TestAggregateTopByFunction tests expect the resulting "top report" to be in a specific order, but the way the top report works it does not guarantee a consistent order. By default, the top report result should probably be sorted by descending by flat value.

$ go test -run TestAggregateTopByFunction
--- FAIL: TestAggregateTopByFunction (0.00s)
    --- FAIL: TestAggregateTopByFunctio