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

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.

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

Describe the bug
If Loki Recording Rules are used with remote-write to a Prometheus instance, which does not have remote-write enabled (--enable-feature=remote-write-receiver), then Loki will fail to remote-write to Prometheus and fail silently.
I have tried this with log-level info, which should include any such e

It seems like the recording rule panel doesn't have the necessary styling applied to it in the dark mode:

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

It is not possible to define SecurityContext for Containers of Alermanager (only PodSecurityContext is available). Because of the missing Container SecurityContext it's not possible to setup important sec

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

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...