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.

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

Is your feature request related to a problem? Please describe.
With the yaml based config and options inherited from cortex etc its easy to make mistakes in the loki config file that don't manifest until runtime. Right now the only way to test the config, per the team on Slack, is to run loki on it. This is fine for a manual check but it becomes difficult to work with in CI environments.

Thanos, Prometheus and Golang version used:
Thanos: v0.15
Prometheus: 2.21

In multiple places, including the sidecar docs, I have seen the following statement.

The --web.enable-admin-api flag is enabled to support sidecar to get metadata from Prometheus like external labels.

It doesn't appear, however, th

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

@bwplotka introduced a new streaming remote read in Prometheus, we should add the same to Cortex for people who point Prometheus and Thanos at Cortex.

We have a flaky unit test which might be just the way we have setup the unit test or an actual problem with how we generate the series, where labels are expected to be in one order but we get them in reverse. In any case we should make it be a deterministic order.

Example: https://github.com/kubernetes/kube-state-metrics/runs/1181030112

--- FAIL: TestFullScrapeCycle (1.07s)
main_test

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