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

We should provide multi-architecture Docker images of skywalking-eyes, just like other SkyWalking sub-projects.

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• [

Currently, we log a debug message when the configured bundled package directory is not readable, but we emit this message whenever we attempt to read the bundled package directory. An improvement here would be to check for the existence of this directory once during Kibana setup, log if it doesn't exist, and not log again. The bundled package lookup process can silently error if this configured di

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

After the Patternfly update we lost the "Info" icons in the yaml editor. We need to fix this regression.

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         

In an effort to make finding the state of each component easier, the README for each component should contain a table which includes:

• stability level
• supported pipelines
• distributions which contain the component

See open-telemetry/opentelemetry-collector-contrib#10006 for an example table with embedded links:

| Status                   |           |
|