+1 best. shown
zhaoqingran <[email protected]> 于2025年8月31日周日 23:06写道： > Hi all, > > TL;DR I propose creating a new Git repository under Apache HertzBeat for a > Go-based collector: apache/hertzbeat-collector-go. I’d like to proceed via > lazy consensus over 72 hours. If there are no binding -1 votes within 72 > hours, I will file an INFRA ticket to create the repository. > > Motivation > > - Build a Go-based collector to improve single-binary deployment, > concurrency, resource usage, cross-platform distribution, and ecosystem > integration (cloud-native/edge). > > Proposed repository > > - Name: apache/hertzbeat-collector-go > - Description: Go-based collector for Apache HertzBeat > - GitHub/GitBox: yes (under github.com/apache, following GitBox > permissions) > - Permissions: all project Committers get write access per GitBox/LDAP > defaults > > Scope and boundaries > > - Collector-only: protocols plus adapters/plugins; no server/UI code. > - Aim for compatibility with existing metrics/protocols where feasible; > provide migration guidance where needed. > - Initial focus: HTTP/HTTPS, TCP, ICMP Ping, JMX, SNMP, Prometheus > scrape, and several common component adapters. > > Maintenance and releases > > - Maintainers: HertzBeat PMC/Committers. > - License: Apache License 2.0; ensure third-party dependency compliance. > > Relationship to existing code > > - Independent sub-repo; no impact on existing repositories. We will > document integration and usage. > > Process > > - This thread runs under lazy consensus for 72 hours. > - If there are no binding -1 votes within 72 hours, I will open an INFRA > ticket to create the repo and share the link here. > > Feedback requested > > - Naming preference (hertzbeat-go-collector vs hertzbeat-collector-go) > - Initial scope and priority of adapters/protocols > - Default notifications and merge strategy settings > - Any risks or concerns > > Please share your thoughts and your +1/0/-1. Thanks! > > Best, Logic >
