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:
Total bytes processed was removed in grafana/grafana@1c838f5 as this was considered temporary solution before we implement Inspector. However, based on feedback, this is valuable information for every query and therefore we should bring it back.

We have Linux monitoring, metrics collected by Prometheus and Zabbix agents. Some people in the community are asking about monitoring Windows OS, which is not very popular in service backend deployment, but still have some.
If someone new to SkyWalking or anything, want to take a reference from existing Linux monitoring and add this feature. We are welcome to accept.

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

Prometheus have this from January, it was added to Alertmanager this week too. I think it's time to add it to Thanos too (:

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?

alertmanager-generated secret created from alertmanagerconfig CRD is missing the global slack_api_url section causing an error in the alertmanager pod when trying to load the new config.

Did you expect to see something different?

Yeah, slack_api_url populated.

How to reproduce it (as minimally and precisely as possible):

Create alertmanagerconfig CRD using

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

What happened?

Starting with Prometheus operator v0.47.0, --config-reloader-cpu and --config-reloader-memory are deprecated and replaced respectively by --config-reloader-cpu-limit/--config-reloader-cpu-request and --config-reloader-memory-limit/--config-reloader-memory-request.

**Enviro

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