We should provide multi-architecture Docker images of skywalking-eyes, just like other SkyWalking sub-projects.
No response
No response
We have two security-related pages that are rendered on the server-side: UnauthenticatedPage and [ResetSessionPage](https://github.com/elastic/kibana/blob/1bfeab7553899efcfa9a6e46b37dc3c7681dcf3b/x-pack/plugins/security/server/a
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.
Add a network option in creating workload
like rancher‘s Networking tab
** During workload creation, user can customize own hosts and DNS search doma
When the backend API responds with 500 error code then the loader on charts section loads infinitely
Charts should show No Data like in trace table.
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
示例
What happened:
I created a pod with a "com.acme/fooBar" label.
The l
Is your feature request related to a problem? Please describe.
I want to install Pixie from an Infra as Code pipeline or from a git repo that I am syncing config from to n clusters.
Describe the solution you'd like
It would be great if this install style were documented somewhere.
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
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
Add a description, image, and links to the observability topic page so that developers can more easily learn about it.
To associate your repository with the observability topic, visit your repo's landing page and select "manage topics."
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