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

Description

I am using InfluxDB as the storage, the InFluxDB is provided by cloud provider, it does't has admin privilege.
If SkyWalking try to create database, it will fail.
I think, SkyWalking should check if the database exi

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?

I was trying to prepare a for loop to do rewrites and accidentally did rewrites on blocks that were marked for deletion. This ended up creating overlaps which prevented compa

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

Bug description

Please describe.
If this affects the front-end, screenshots would be of great help.

run production build in local server

Expected behavior

write a script while will run the production build locally (production build=>/build)

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