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.

What would you like to be added:

Currently, some headings are also steps in procedures. The format is not consistent. We need the heading format made consistent per the Grafana documentation style guide.

This means both the step number format (Step 1., Step 2.) and that everyt

Move all Dockerfile samples to non-root user

Expected Behaviour

As an OpenFaaS end-user, I want to run all samples on my OpenFaaS cluster, even with the new non-root feature enabled.

Current Behaviour

Hello Loki team,

First and foremost, thank you so much for Loki! It's awesome.

Is your feature request related to a problem? Please describe.
As a cluster administrator, when installing loki-stack
I want to be able to set toleration for promtail
So that I may forward logs from all nodes, even nodes with taint, to loki

Describe the solution you'd like
I would like to be able to

Context: https://twitter.com/bwplotka/status/1334404169432788992

Help wanted 🤗

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

In the documentation user-guide for linting, the example script's docker command is broken.

It seems like the docker command broke since the image was changed.

The following command does work, and I would be happy to modify the script to imp

There are a few things I noticed while following @codesome's Rawkode podcast: https://www.youtube.com/watch?v=lI-4jHKv2Y0

• People need to install Golang, and compile Cortex/Prometheus for them to run through the getting started guide. This is not trivial at all even for Prometheus, we need to install node and yarn for asset compilation. We should be using release binaries instead.

• **P

This is a FEATURE REQUEST.

Please add support for kube_state_metrics_build_info as part of the metrics exposed on telemetry port 8081.
kube_state_metrics_build_info shall include the version of the kube-state-metrics.
Most Prometheus exporters are currently supporting such metric.

What is missing?
Not all objects created with kube-prometehus have recommended set of labels

Why do we need it?
To comply with best practices and allow easier dependency discovery

Environment

• kube-prom

blackbox_exporter version:

10b04fc9fd220343938233c5586556f7e84a2f45

What is the blackbox.yml module config.

modules:
  http_proxy_sna_monitor:
    prober: http
    http:
      fail_if_body_not_matches_regexp: ['{"status":"ok","components":[']

logs

ts=2020-12-02T09:22:07.826147753Z caller=http.go:

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