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

Update our screenshots and the names of some of the options may have also changed

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

Java Agent (apache/skywalking-java)

What happened

we config trace ignore paths by "agent/config/pm-trace-ignore-plugin.config", but found paths ends by "/" are not ignored with "**".

example configuration i

Hi.
Could you please add parameter limits_config.max_concurrent_tail_requests to the documentation?
Also not sure if default value 10 is big enough.

Thank you.

Is your proposal related to a problem?

When a Compactor halts due to an out-of-order (OOO) block, there are normally several OOO blocks that need to be tidied up before Compactor can safely run again. At the moment, Compactor only tells me about the first OOO block that it finds - so I need to go through quite a long cycle of identifying a broken block, deleting the broken block, and restar

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

Is your feature request related to a problem?

Currently, installing SigNoz requires having/installing docker. This maybe too much of an overhead if someone is just testing out SigNoz. We should make this process much simpler so that more people can try out SigNoz.

Describe the solution you'd like

Providing single binary application could be one way to reduce this friction

Prometh

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