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

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• Question or discussion

Question

I'm able to send traces via TLS but when I try to send logs, I get the following exception:

ERROR 2021-05-30 22:21:59:387 grpc-default-executor-1 GRPCLogReportServiceClient : Try to send 1 log data to collector, with unexpected exception.
org.a

Is your feature request related to a problem? Please describe.

my /var/log directory has files with different structures, which requires me to use different pipeline_stages for each set of different files.

Describe the solution you'd like

something like this would exclude all files that match the pattern /host/var/log/contained.*.log:

    static_configs:
      - 

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

Is your proposal related to a problem?

Replication is currently slow.

Describe the solution you'd like

tools bucket replicate could upload a few objects at a time instead of one by one

Describe alternatives you've considered

Copying the objects with some other tool but tools bucket replicate is way too convenient because you can use two completely different object st

It will be very useful to have timezone info exposed in node exporter.
For example this info "Time zone: Asia/Jerusalem (IDT, +0300)"

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

In this document, following sentence has a typo,

# Register the intrumentation handlers (/metrics etc).

intrumentation -> instrumentation

# Register the instrumentation handlers (/metrics etc).

Current Behaviour

The flamegraph sorts the siblings in ascending order by frame's name.
The reference to code is here

Expected Behaviour

The siblings should appear in order of their start time.
This can be achieved according to library docs mentioned [here](https://github.com/spiermar/d3-fla

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