observability

Bug description

netdatacli has limit for output size of 4096

Expected behavior

do we just increase this limit or make it transfer arbitrary message sizes?

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?

• [

When a user searches for a value on the cases list page the UI does not pass any search_fields value. This causes Elasticsearch to query all available fields within the case saved object. This could cause some confusion as to why some cases are returned in the search results because we don't display all the data from a case in the UI.

References: https://github.com/elastic/kibana/blob/main/x-

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

The current overview section in the application detail page has 4 charts which need to move from promQL to query-builder APIs. Below are the charts on that page:

1. Application latency
2. Requests
3. Error Percentage
4. Top Endpoints

edge is grouped correctly, but the icon is wrong (it should be a folder).

To reproduce, mock the /label-values?label=__name__ response to

[
  "edge",
  "edge.alloc_objects",
  "edge.alloc_space",
  "edge.block_count",
  "edge.block_duration",
  "edge.cpu",
  "edge.g

可以通过在当前 issue 登记您的使用情况，并分享您使用夜莺监控的经验，将会自动进入 END USERS 列表，并获得社区的 VIP Support。

示例

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

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

Is your feature request related to a problem? Please describe.
On https://work.dev.withpixie.dev/configure-data-export/
Users reading the export script view will find that the status icon to be in an unknown state - signaling a system error. In reality, we're just not querying the state of the plugin script because it is disabled.
<img width="644" alt="image" src="https://user-images.githu

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 npmlog@6.0.2: The engine "node" is incompatible with this

After running Parca@parca-dev/parca@ffa8368 for some minutes, this error message started showing up many times:

Describe the bug
The link to the receiver helper content is broken.

Steps to reproduce

1. Go to https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security.md#receivers-and-exporters.
2. Click the link for receiver.

What did you expect to see?
Content for the receiver helper function

What did you see instead?
A 404 error page
<img width="1512" a