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

^{Originally posted by sunker December 17, 2021}
When support for Metrics Insights was added to the GetMetricData api, a few new error codes were introduced. These should be handled as an error or possibly as a warning.

![Screenshot 2021-12-09 at 18 46 54](https://user-ima

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:

Host operating system: output of uname -a

Linux sarbian 5.13.5-arch1-1 #1 SMP PREEMPT Sun, 25 Jul 2021 18:02:58 +0000 x86_64 GNU/Linux

node_exporter version: output of node_exporter --version

node_exporter, version 1.2.0 (branch: tarball, revision: 1.2.0)
build user: someone@builder
build date:
go version: go1.16.5
platform: linux/amd64

n

What is missing?

Labels in CRDs me

Some users want to use SigNoz for WSL

We don't have official support for it as of now, but would be great for somebody to test this and report findings.

In this document, following sentence has a typo,

# Register the intrumentation handlers (/metrics etc).

intrumentation -> instrumentation

# Register the instrumentation handlers (/metrics etc).

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