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 ] Question or discussion
• Bug
• Requirement
• Feature or performance improvement

Question

• Need to post Alarm to https , How to provide header. Also how to get the Hostname along with Alarm.
  For example need to post the alarms through

curl -X POST
https://***

Part of elastic/kibana#91715

In
https://github.com/elastic/kibana/blob/master/x-pack/plugins/lens/public/indexpattern_datasource/loader.ts#L338-L342

the list of index patterns is loaded via saved objects client.

This should be replaced by using the getIdsWithTitle method of the index pattern service.

I find a solution in the forum
https://kubesphere.com.cn/forum/d/3384-kubespheredevopsdotnet-core
But it is too trouble to use , and waste much time to set up it .
So any plan for including it to the nodes of devops flow.

I recently(ish) bumped client-go and other deps in the release-2.0 branch but did not have a chance to port these changes to master as well. I believe this is a good first issue for new contributors.

This is the original PR that needs to be ported to master branch. kubernetes/kube-state-metrics#1328 Note master branch does not have the vendor directory anymore.

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.

Community Call To Action

Feel free to open PRs, even if it's one or two small fixes. This kind of work is important but often overlooked. This is a great way to learn more about the internals of the project and we'd appreciate any help on this.

Summary

We use revive as the main linter.

How to tackle these

Run the linter. It will print

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:

As we are trying to make SigNoz deployment to work in common infra setups, a good first issue could be just trying installing SigNoz in their local setup and sharing if they face any issue.

Please share your infra details and did you face any issue in running SigNoz

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?