GitHub user fanfuxiaoran added a comment to the discussion: Introducing the 
[perfmon] Extension for Cloudberry Database Monitoring​




> @fanfuxiaoran
> 
> Thanks for confirming that `libsigar` is still in use. However, I’d strongly 
> encourage us to reconsider that position. Continuing to depend on `libsigar` 
> **without any plan to replace or modernize it** introduces significant risks 
> to the Cloudberry project:
> 
> ### ❌ Why `libsigar` is problematic:
> * **Unmaintained**: No upstream development or security patches in years.
> * **Broken on modern platforms**: Build issues are common on RHEL 9, Debian 
> 12, Alpine, macOS, etc.
> * **Difficult to patch**: Contributors will be forced to debug outdated C 
> code and platform-specific breakage.
> * **Portability blocker**: This limits adoption on modern developer 
> workstations, CI systems, and containers.
> * **ASF sustainability concern**: Bringing in obsolete dependencies violates 
> the spirit of maintainability and long-term openness expected in ASF projects.
> 
> ### ✅ What we need:
> If `perfmon` is to become a core part of Cloudberry’s monitoring 
> infrastructure, we should at minimum:
> 
> * **Track this as a known technical debt item**, with a defined migration 
> path or plan to deprecate `libsigar`
> * **Abstract `libsigar` usage** behind an interface, so it can be replaced in 
> a modular way
> * **Evaluate modern replacements**:
>   
>   * `/proc`-based stat readers (Linux-only, but simple)
>   * Integration with system libraries like `libstatgrab`, `psutil`, or 
> systemd APIs
>   * Shell out to `vmstat`, `iostat`, or `/sys/fs/cgroup` metrics as a fallback
> 
> Without a plan, we risk adopting legacy constraints that will slow down 
> contributors and users alike.

Agree. I will try libstatgrab to see if it can replace libsigar in gpsmon

GitHub link: 
https://github.com/apache/cloudberry/discussions/1087#discussioncomment-13060977

----
This is an automatically sent email for dev@cloudberry.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@cloudberry.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cloudberry.apache.org
For additional commands, e-mail: dev-h...@cloudberry.apache.org

Reply via email to