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

The plugin HttpPlugin of nodejs agent not intercept the method http.get

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Describe the bug:
Old name package in error message while adding existing agent policy for Endpoint Security integration.

Build Details:
VERSION: 8.2.0-BC4
COMMIT: 9a5003d8cf0062bf24ef64d6712b44823888cc03
BUILD: 52005
ARTIFACT LINK: https://staging.elastic.co/8.2.0-3b2b9b86/summary-8.2.0.html

Preconditions:
Elastic 8.2.0-BC4 environment should be deployed.

**Steps to R

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

When the backend API responds with 500 error code then the loader on charts section loads infinitely

Expected behavior

Charts should show No Data like in trace table.

Version information

we should add a minimum width so these don't expand vertically like this

示例

• 企业或者组织: 夜莺
• 地点：北京
• 联系方式：contact-us at xxx.com
• 使用场景和经验分享：你们最看重夜莺的哪些功能，解决一个什么样的问题，以及使用规模和范围，使用夜莺监控构建企业级监控体系的过程中，有哪些好的经验分享。
• 需求建议：希望哪些点上夜莺监控能做的更好，更契合您的使用场景。

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

Describe the bug
During the lifetime of my application, everything is working properly.
Once I closed it, I have a "warning" in the collector:

warn zapgrpc/zapgrpc.go:191 [transport] transport: http2Server.HandleStreams failed to read frame: read tcp [::1]:4317->[::1]:64933: wsarecv: Une connexion existante a dû être fermée par l’hôte distant. {"grpc_log": true}

"Une co

While setting up Parca for prometheus' prombench, I had to configure all the profiling configs, because we use a prefix.

Since the prefix is common to all, it would be useful to be able to provide the prefix.

instead of:

    profiling_config:                                                      
      pprof_config:
       memory_total:        
               enabled: true         

Description

Now we connect jira / gitlab on Domain Layer level, compound plugin is not needed anymore.

Describe the solution you'd like

• Finish #1020 first
• Remove compound plugin from Backend
• Remove setting following setting from config-ui
  

Has