observability

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.

Please answer these questions before submitting your issue.

• Why do you submit this issue?
• [ x ] Requirement

Question

• java agent support dubbo 3.0

The Filters aggregation is not supported on rollups, and the Top values aggregation does not work on meta fields like _index the same way it works regularly. So this causes 4 places that rollups should be restricted more:

1. No Filters bucket aggregation
   <img width="564" alt="Screen Shot 2021-06-30 at 4 48 44 PM" src="https://user-images.githubusercontent.com/666475/124029867-9b29f380-

I have been asked several times whether the value filled in cc.spec.common.es.externalElasticsearchUrl requires an http prefix, but it is actually not needed, but this key is a bit confusing. I don’t know if I need an http prefix sometimes when I look at it, so I think it’s clearer to change it to externalElasticsearchUrl to externalElasticsearchHost

/kind feature-request

Summary

Go 1.16 was released in February and the feature we're most excited about is go:embed. Relevant articles:

• https://golangtutorial.dev/tips/embed-files-in-go/
• https://golang.org/doc/go1.16
• https://golang.org/pkg/embed/

Currently we use pkger to embed web app assets into the binary. This is only enabled in production builds.

Objective

Switch from pkger to

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

Kiali uses tooltip in multiple locations, in some cases style difers even for the same concepts.

I noticed some changes on this kiali/kiali-ui#1884 but it would require some global issue to review all tooltips and check that they look like similar (at least for the same concept).

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:

Has anyone done this safely?