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.

Kibana version: master

Describe the bug: When the value of a metric visualization is 0, it's just displayed as a dash.

Steps to reproduce:

1. Ingest 0 data:

POST data/_doc
{
  "numberfield": 0
}

2. Create indexpattern for data
3. Go to Lens
4. Drag numberfield
5. Average metric is shown as "-"

Expected behavior:
Should be shown as 0

**Screenshots

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• [] Question or discussion
• Bug
• Requirement
• Feature or performance improvement

Question

org.springframework.kafka.KafkaListenerEndpointContainer#0-4-C-1 InstMethodsInter : class[class org.postgresql.jdbc.PgPreparedStatement] before method[executeWithFlags] intercept fai

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

Is your feature request related to a problem? Please describe.
when I run yarn start on local what ubuntu system , the error happen in page

when I run build

**D

Cloudprober supports building additional metrics (other than the default ones) from external probe output. We could possible do the same for HTTP probe.

Why: When opening the Event Injection modal for a particular eventBus, the tool populates each field (source, detail type, and detail) with the last values used for that eventBus. Allowing all events to be saved, similar to the command history in the terminal, will allow users to quickly test multiple events without having to type the same parameters repeatedly.

Expected Behaviour:

Description/Screenshot
enableAutoRouteTracking: true should update ai.operation.name to include the hashroute in the pathname

https://github.com/microsoft/ApplicationInsights-JS/blob/ae71ebf806da82e149b0af60f00d70b2c1d3e3f0/extensions/applicationinsights-analytics-js/src/JavaScriptSDK/ApplicationInsights.ts#L650-L653

Describe the bug
Deploying a new job, then pulling logs via the CLI results in a panic (SIGSEGV).

To Reproduce

1. odin deploy -f test.job.yaml
2. odin log -i {job_id}

vagrant@vagrant:~/odin$ odin log -i dea194794589
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x79c764]

goroutine

Has anyone done this safely?

It'd be nice if the various README's referenced and gave instructions for tanka instead of ks (since that's now a dead project, right?).