We should provide multi-architecture Docker images of skywalking-eyes, just like other SkyWalking sub-projects.
No response
No response
The work to introduce user profile support has nearly doubled the size of our page load bundle (elastic/kibana#132522). We are just barely under the 100kb suggested limit after these changes, so we should work to bring this down to a more comfortable level.
<img width="598" alt="CleanShot 2022-06-01 at 14 04 35@2x" src="https://user-images.githubusercontent.com/3493255
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
After the PF4 update, some styles would need an adjustment, this issue is to track a minor change in the trace details labels:
On green/red labels, the font color should h
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
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