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

PagerDuty(https://www.pagerduty.com/) is widely used for on-call globally. We are welcome the contributions to support it as alarm notification channel.

Kibana version: 8.1.0

Elasticsearch version: 8.1.0

Server OS version: darwin_x86_64

Browser version: chrome latest

Browser OS version: OS X

Original install method (e.g. download page, yum, from source, etc.): from staging

Describe the bug: Lens "click here to create dataview" screen should also mention to the user about the option to switch the dat

Add a network option in creating workload

like rancher‘s Networking tab

** During workload creation, user can customize own hosts and DNS search doma

Description

1. The theme change toggle's placement is incorrect as it is being placed at the most important place i.e. top left, ideally it should be place in the top right as it's not the highlight of the product.

2. There

Given that I am in the page /comparison-diff

https://demo-dev.pyroscope.io/comparison-diff?query=cart.service.dotnet.cpu%7B%7D

Problem seems to be that we are not doing an exact match here
https://github.com/pyroscope-io/pyroscope/blob/main/webapp/javascript/co

What would you like to be added:

Add UID as a label, like it is on some other metrics, to all service metrics.

Why is this needed:

This is valuable since load balancer services in clouds often use the UID as the name of the cloud load balancer; however, there's no easy way then to join those metrics in say

It would be helpful to add a 'Download' (to file) option to the Kiali Debug information view, instead of having to copy/paste into a file.

threadcreate profiles have been broken in Go since 2013, and it doesn't seem like they'll be fixed in any shape or form anytime soon.

For the sake of not confusing users, we should remove threadcreate from being scraped by default. (it also triggered confusion causing us to ignore empty stack traces, eg. #666)

golang/go#6104