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.

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

We have a promtail configured with two scrape configs: consulagent_sd_configs & systemd-journal
Inspecting the output from the metrics at /metrics, it seems that Promtail only exposes data relevant to file-based log tailing.

There is no data about metrics that were collected via the systemd-journal target at all.
I'm not even sure if the total metrics such as

• `promtail_targets_a

Thanos, Prometheus and Golang version used:

Thanos v0.25.0

Object Storage Provider:

Azure

What happened:

When running thanos tools bucket verify... against an object storage that is actively compacted, it returns a large number of "warning" logs containing information on overlapped blocks. On closer inspection, these overlaps are between blocks of different levels of

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

Bug description

Header in Top Endpoint section overflows in browser with reduced width

Expected behavior

Header shouldn't overflow

How to reproduce

1. Go to SigNoz dashboard metrics page with reduced browser window width
2. Open any application
3. Top Endpoint panel header appears overflowing

Version information

• Signoz version: v0.7.1
• *Browser version

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