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.

Currently the decorator @trace only support plain functions. Decorating functions with async makes the trace hierarchy incorrect.

        @runnable()
        async def test1(self):
            return '1'

        @runnable()
        async def test2(self):
            return self.test1()

        def test(self):
            asyncio.run(self.test2())

this generates

For context variables provided by an alert, to be used in action parameters, usually the values of the variables are strings or other primitive values. However, they can be objects as well. The metrics alert makes use of this for it's grouping (I believe).

When a customer uses these object-valued variables directly as a mustache "variable", mustache will render these values as the following,

Feature Description

Kubersphere integrate the velero based on the k8s CRD extensions

How does it work
It's like monitoring component

This is a FEATURE REQUEST.

Please add support for kube_state_metrics_build_info as part of the metrics exposed on telemetry port 8081.
kube_state_metrics_build_info shall include the version of the kube-state-metrics.
Most Prometheus exporters are currently supporting such metric.

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