prometheus

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

Steps to reproduce:

Try to collapse the Explore query row using keyboard-only navigation

Actual Result:

Can’t collapse query row

Also, there is a focus-issue here. See the A11y notes:

Same tab, when you copy the query or a link to it, the focus is reset

Expected Result

We already have some scripts in the scripts directory. It would be good to run them for every PR.
This is also a great task for beginners.

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

The plugin HttpPlugin of nodejs agent not intercept the method http.get

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Is your feature request related to a problem? Please describe.
CEF (Common Event Format) is a logging format used by some tools. Loki and promtail should have a built in parser for it so that I can extract CEF fields as labels.
CEF messages look something like:

CEF:0|Palo Alto Networks|Cortex XDR|Cortex XDR 2.4|X

The idea originated from this comment, see for full context thanos-io/thanos#4908 (comment)

Basically, we could improve the user experience by providing more information on how the stores are being queried, beyond providing just min / max time or just showing that the min / max time is not available, which does not in fact tell users if that store will be que

Host operating system: output of uname -a

Linux xyz 4.18.0-358.el8.x86_64 #1 SMP Mon Jan 10 13:11:20 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

node_exporter version: output of node_exporter --version

node_exporter, version 1.3.1 (branch: tarball, revision: 4.el8)
  build user:       
  build date:       20220128
  go version:       go1.16.12
  platform:         linux/amd6

What is missing?
CRDs don't provide a short name

Why do we need it?
Convenience :)

Anything else we need to know?:
I think it's quite common to provide short names for CRDs nowadays:

• keda.sh: ScaledObject: Short Names: so
• autoscaling.k8s.io: VerticalPodAutoscaler: Short Names: vpa
• cilium.io: CiliumNode: Short Names: cn

Spent the morning debugging what I thought was a goroutine leak, but turned out to be just a huge number of goroutines being created in a short period of time. However, it seems a lot of the unit tests do leak goroutines. Most of these might just be issues with tests not cleaning up properly, but it makes testing/debugging real leaks quite difficult. Or in my case, the leaks were a red herring - t

README.md is still pointing to addons/strip-limits.libsonnet addon as a way to strip containers from set resource limits. However since release-0.8 resource requests are first-level settings and users should use

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

What did you expect to see?

I'm expecting to be able to filter out the requests from blackbox exporter in my access logs.
So, please, add a user agent header that container the "blackbox exporter" string somewhere.

What did you see instead?

I see User-Agent: Go-http-client/1.1
Not easy to filter in the access logs...