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

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?

• [

Kibana version: 8.3

Description of the problem including expected versus actual behavior:

• Can we change "Unsaved changes" badge color to a warning color instead?
• It would be great to add a tooltip to the badge and suggest what to do to save those changes.

Steps to reproduce:

1. Create a dashboard and add a visualization
2. Edit visualization
3. Notice that "Unsaved c

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

Filtering dashboards based on specific titles does not work. for e.g. Titles with parenthesis

Expected behavior

The filtering of dashboards should work seamlessly irrespective of filtering of dashboards

How to reproduce

Attached loom video

Version information

• Signoz version:v0.8.1

The contrast is not very good
As you can see the contrast is not very good
https://github.com/pyroscope-io/pyroscope/blob/main/packages/pyroscope-flamegraph/src/FlameGraph/FlameGraphComponent/colorPalette.ts#L34

Plus it's a good idea to have a look at every single color in the pal

示例

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

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

Describe the bug
I'm attempting to deploy Pixie into a k3s cluster which is listed as supported in the Pixie docs.

The Cluster type is supported check passes, but then fails later saying the cluster type isn't in the list of known supported types.

I'm able to manually proceed with the dep

After upgrade node to the latest one I got the message that node engine must be >=12.22.0 and < 16. this is great because we set in the package.json:

"node": ">=12.22.0 && <16"

So I installed the latest 15.X 15.14.0 (latest one of 15) and I got :

`error [email protected]: The engine "node" is incompatible with this

In subsequent PRs. We should add integration tests for debuginfo.Store.Exists and debuginfo.Store.Upload using the debuginfo.Client.

Originally posted by @kakkoyun in parca-dev/parca#1157 (comment)

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