leborchuk commented on PR #1713: URL: https://github.com/apache/cloudberry/pull/1713#issuecomment-4369362599
This is just a remark. There is no need to fix anything here. Also, consider doing the same thing outside the cloudberry database code. We have a command center and information about requests being executed and their execution plans get there. It is much more convenient to analyze queries and other metrics in the command center rather than in an extension: 1. This is a separate process. It's easier to update the shared library. The whole cloudberry instance needs to be restarted. It often happens that something needs to be fixed quickly and rolling out a new version of an extension with a cloudberry restart takes a lot of time. 2. The process is written in Go. It's very easy to add new functionality - sending data to Kafka topics, coordinating actions of administrators, etc. Our operational experience shows that simple rules aren't enough and the rules need to change over time for each installation and analyst team in a unique way. And a companies with large installations prefers to create their own rules. Here [gp_stats_collector ](https://github.com/apache/cloudberry/tree/main/gpcontrib/gp_stats_collector )is the source code for the extension that sends data from Cloudberry to the outside. [Here](https://github.com/open-gpdb/yagpcc) is the outside agent go code itself, which accepts and processes the data from the extension. The code is not yet in the Apache repository, but I plan to finish it this month and present to the community. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
