Feature idea summary

Cgroups plugin supports only proportional and max Block IO policies. We should support BFQ scheduler as well. Disk stats for the scheduler are in blkio.bfq.io_service_bytes and blkio.bfq.io_serviced files.

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Feature or performance improvement

Question

• What do you want to know?
  I look into jedis-2.x plugin, find that enhanceClass is redis.clients.jedis.Jedis.
  But pipeline will directly invoke jedis client.
  Jedis --invoke---> client
  pipeline ---invoke-->client

There are two solutio

https://github.com/heptiolabs/healthcheck

This will give us metric on healtcheck and more granularity on checks we want to have.

/cc @slim-bean @joe-elliott

As stated in the title, we need to add basic promtool tests for all the alerts we have in mixin. At the very least, they will help us to catch templating issues with our alerts.

This is a reminder for me or a task if anyone wants :P

Basically, The last two questions aren't really regex's questions.

To do:

• Move said questions to correct place.
• Add new regex questions (Python related!)?
• Maybe add a new ## Regex section, as it is a valuable skill

What happened?

After being fine for a couple days, Prometheus mysteriously started crashing with this error:

level=error ts=2020-09-02T15:16:55.096Z caller=query_logger.go:87 component=activeQueryTracker msg="Error opening query log file" file=/prometheus/queries.active err="open /prometheus/queries.active: permission denied"
panic: Unable to create mmap-ed active query log

goro

Is your feature request related to a problem? Please describe.
It's very easy to see ingester and ha ring status, but distributor ring status is only sort of viewable via Consul

Describe the solution you'd like
A status page that shows the distributor ring status similar to how we can currently view ingester ring status.

Describe alternatives you've considered
Currently I ta

I recently(ish) bumped client-go and other deps in the release-2.0 branch but did not have a chance to port these changes to master as well. I believe this is a good first issue for new contributors.

This is the original PR that needs to be ported to master branch. kubernetes/kube-state-metrics#1328 Note master branch does not have the vendor directory anymore.

What is missing?

I was chatting with @paulfantom and we were thinking of having a first-class field in our top level configuration called platform that applies the respective platform specific patch automatically, instead of people having to understand how to use it in jsonnet.

**Why do we need it

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

It would be awesome if the metrics could include the node's topology.kubernetes.io/region & topology.kubernetes.io/zone (not sure what the non-AWS fields are called). That would help quickly identify patterns in the results. e.g., zone "a" is slower than zone "b" or that cross-zone traffic is what's causing a large spike in response times. Not sure if this is possible within the framework of this