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.

This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

@kezhenxu94 I think with using graceful shutting down, we need a simple e2e to verify whether OAP and UI could be shut down successfully. Because, once we have one unexpected thread, the shutdown wouldn't work.

Originally posted by @wu-sheng in apache/skywalking#7020 (comment)

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

Is your proposal related to a problem?

Moving from Prometheus to Thanos and I am now noticing that Ruler does not show alert rule duration in the UI like Prometheus would show. I think it is important to show this

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

po-lint was useful when there was no tools like kubeconform (which we use in kube-prometheus project). And support for CRDs in kubernetes was at earlier stage. Right now po-lint seems like a largely unused code.

We would need to change docs at https://github.com/prometheus-operator/prometheus-operator/blob/master/Documentation/user-guides/linting.md

Some of our tests are slow. Here is list of packages with tests that run above 5 seconds (from https://github.com/cortexproject/cortex/runs/2054589567 run).

227.510s    github.com/cortexproject/cortex/pkg/ring
213.005s    github.com/cortexproject/cortex/pkg/querier
60.907s github.com/cortexproject/cortex/pkg/ingester
60.674s github.com/cortexproject/cortex/pkg/storegateway
42.779s gith

What happened?
I wanted to configure my kubeadm-like cluster to get monitored by prometheus-operator. I started using the following file:

apiVersion: kubeadm.k8s.io/v1alpha1
kind: MasterConfiguration
api:
  advertiseAddress: 192.168.1.173 (I changed the IP from here)
  bindPort: 6443
authorizationModes:
- Node
- RBAC
certificatesDir: /etc/kubernetes/pki
cloudProvider:

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