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.

We have Linux monitoring, metrics collected by Prometheus and Zabbix agents. Some people in the community are asking about monitoring Windows OS, which is not very popular in service backend deployment, but still have some.
If someone new to SkyWalking or anything, want to take a reference from existing Linux monitoring and add this feature. We are welcome to accept.

Relates to #95876 fixed by PR#95939.

When a step (index settings) is invalid, it's possible to navigate to the previous step (logistics) by clicking its name in the wizard top navigation bar. That way the wizard will be blocked on the 1st step with a disabled 'next' button.

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

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.

Providing a single click Heroku deploy option may be a good idea to make it easy to test SigNoz for developers.

Tasks

• Check if current SigNoz docker can run in Heroku free tier and the compute requirements are served in the free tier of Heroku. Goal is not to test with high load but to get the application up and running with sample Hot ROD application

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:

Currently, JavaScript SDK logs status code 0 when the connection between the client and server cannot be resolved. This makes diagnosing network errors very difficult, as there are many different problems that can cause 0 status code in failing dependency calls.

The proposal is to log status code information that indicates whether a network error occurred and what type.