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

What happened:

When creating a Slack contact point, I am unable to save unless the Webhook URL field is populated. However, right above the field, it says that the field is optional. This doesn't make sense.

Also, if you are trying to make a token-based (non-webhook) Slack bot, this bug makes it impossible. Token-based bots must have a blank webhook URL, or it'll try to send it as a we

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

We should provide multi-architecture Docker images of skywalking-eyes, just like other SkyWalking sub-projects.

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• [

Is your feature request related to a problem? Please describe.
My k8s cluster doesn't use cluster.local, but this is hardcoded in many places in the Tanka libsonnet files. I have to change this every time I upgrade.

Describe the solution you'd like
A variable I can specify in main.jsonnet that will be used instead. This is actually the change I make now and it seems to work fine. I'

On https://thanos.io/tip/thanos/changelog.md/ -> Table of Contents

This link v0.25.2 - 2022.03.24 should actually go towards https://thanos.io/tip/thanos/changelog.md/#v0252httpsgithubcomthanos-iothanostreerelease-025---20220324

Perhaps this page / table of contents could be easier/nicer as well - For example that the table of contents

Replace this parsers in node exporter with this ones from procfs.

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

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

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

While setting up Parca for prometheus' prombench, I had to configure all the profiling configs, because we use a prefix.

Since the prefix is common to all, it would be useful to be able to provide the prefix.

instead of:

    profiling_config:                                                      
      pprof_config:
       memory_total:        
               enabled: true