Nikolay Sivko

Unfortunately, we currently have no plans to support WSL.

Unfortunately, in the case of AWS ECS, it is not possible to collect metrics at the node level (because ECS is a serverless solution) and those based on eBPF (due...

@franramb we've implemented basic support for AWS Fargate in Coroot. It's based on metrics collected by Cadvisor integrated into Fargate "nodes". Unfortunately, all eBPF-based capabilities are not working for applications...

Coroot currently does not support attribute search. We plan to add this feature in a future update.

@rmn-lux, starting from version 0.27, Coroot uses ClickHouse to store profiling data. The default TTL is set to 7 days, but you can [adjust](https://github.com/coroot/helm-charts/blob/main/charts/coroot/values.yaml#L114) it if necessary.

Coroot uses cloud metadata to determine the instance Region, Availability Zone, and Instance Type. These parameters can be configured [manually](https://coroot.com/docs/metric-exporters/node-agent/installation). Additionally, Coroot uses cloud pricing data to retrieve the instance...

Coroot currently uses the model generated [here](https://github.com/coroot/cloud-pricing/blob/main/update.go) to get instance prices. Implementing custom pricing may require modifications to the Coroot codebase.

Thanks for the issue report. We're already working on reducing the memory footprint of Coroot.

Coroot 0.12.6 has several performance related improvements. Can you please update it and check the memory usage in your environment?

@Nello-Angelo, could you please check the Prometheus (VictoriaMetrics) scrape interval for the `coroot-node-agent` targets, as well as the refresh interval configured in Coroot (Settings -> Prometheus)? Coroot requires that the...