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

The following tests are outputting errant logs and warnings to the console during unit tests. Some of these are pointing out genuine errors and things that should be looked at, while others might be a bit more benign but should be cleaned up to make testing more pleasant.

In the future we may consider making console logs to be a failure condition in tests, so it would be good to sort these out

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

Apache SkyWalking Component

OAP server (apache/skywalking)

What happened

1. Set SW_PLUGIN_HTTP_INCLUDE_HTTP_HEADERS=x-request-id,x-correlation-id in environment.
2. OAP-Server Set `SW_SEARCHABLE_TAG_KEYS=http.method,http.he

Describe the bug
Only hour (h), minute (m), milliseconds (ms) and second (s) duration format works with the offset modifier but day (d), week (w) and year (y) throws this error = parse error at line 1, col 47: syntax error: unexpected NUMBER, expecting DURATION

To Reproduce
Make the 1d and 1w query visible

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

Can be obtained with sw_vers:

$ sw_vers --help
Usage: sw_vers [-productName|-productVersion|-buildVersion]

$ sw_vers 
ProductName:	macOS
ProductVersion:	12.1
BuildVersion:	21C52

$ sw_vers 
ProductName:	Mac OS X
ProductVersion:	10.13.3
BuildVersion:	17D102

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

Is your feature request related to a problem?

Related to this issue: SigNoz/signoz#716

Describe the solution you'd like

Add support for DESC/ASC param for getFilteredSpans API in query service

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

What is missing?

It might be good to consider running node_exporter pods with priorityClassName: system-node-critical to allow smooth operations in clusters with autoscaler enabled and high resource occupancy.

Why do we need it?

More context in https://kubernetes.slack.com/archives/CFFDS2Z7

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