The report_info_flyout_content has breached a point where it is more convenient for maintainers of the file to source the user-facing content strings from a separate file.
This issue is to follow the imports added in https://github.com/elastic/kibana/pull/130020/files#diff-83b67268eba04e092077b198cf34a3a7c273878024670feac96ca495fc8d829f to hoist all the user-facing content strings from the e
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 message is shown in 2 places, which makes it redundant
Plus it's not styled as if it were an error so it's even more confusing.
示例
What happened:
I created a pod with a "com.acme/fooBar" label.
The l
Some pages give React warnings when you visit them and inspect the dev console. This is probably minor but would be good to resolve.
Services page:
Istio Config details page:
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