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

Transfering @NissesSenap's issue from ViaQ/loki-operator/issues/103

Today the operator only support aws and thus S3 object storage but on the other hand Loki have support for a number of none S3 storage solutions: https://grafana.com/docs/loki/latest/configuration/#storage_config

I know that this operator in a early stage but to make it easier for faster adoption it would be nice to support

With Sidecar now changing its readiness status depending on whether it can establish a connection with Prometheus, there is spam of:

{"caller":"intrumentation.go:48","level":"info","msg":"changing probe status","status":"ready","ts":"2022-01-06T16:37:27.595400008Z"}

We shouldn't print this message if the status is set to the same value as the previous one.

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?

Similar to promet

PHP looks like a less mature OpenTelemetry implementation, but it exists: https://github.com/open-telemetry/opentelemetry-php#installation

If possible, additional instrumentation tutorial for these popular frameworks would be helpful:

1. Zend Framework 3
2. WordPress
3. Silverstripe
4. [Symfony]

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