You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hertzbeat.apache.org by zhaoqingran <zh...@apache.org> on 2025/08/31 15:06:40 UTC

[DISCUSS] Create new repo for Go-based collector: apache/hertzbeat-collector-go (lazy consensus, 72h)

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

Re: [DISCUSS] Create new repo for Go-based collector: apache/hertzbeat-collector-go(lazy consensus, 72h)

Posted by Yang <15...@qq.com.INVALID>.
+1
Best regards,
Yang Chen (陈阳)







         Original
         
       
From: zhaoqingran <zhaoqingran@apache.org&gt;
Date: 2025-08-31- 23:06
To: dev <dev@hertzbeat.apache.org&gt;
Subject: [DISCUSS] Create new repo for Go-based collector: apache/hertzbeat-collector-go(lazy consensus, 72h)



       Hi&nbsp;all,

TL;DR&nbsp;I&nbsp;propose&nbsp;creating&nbsp;a&nbsp;new&nbsp;Git&nbsp;repository&nbsp;under&nbsp;Apache&nbsp;HertzBeat&nbsp;for&nbsp;a
Go-based&nbsp;collector:&nbsp;apache/hertzbeat-collector-go.&nbsp;I’d&nbsp;like&nbsp;to&nbsp;proceed&nbsp;via
lazy&nbsp;consensus&nbsp;over&nbsp;72&nbsp;hours.&nbsp;If&nbsp;there&nbsp;are&nbsp;no&nbsp;binding&nbsp;-1&nbsp;votes&nbsp;within&nbsp;72
hours,&nbsp;I&nbsp;will&nbsp;file&nbsp;an&nbsp;INFRA&nbsp;ticket&nbsp;to&nbsp;create&nbsp;the&nbsp;repository.

Motivation

&nbsp;&nbsp;&nbsp;-&nbsp;Build&nbsp;a&nbsp;Go-based&nbsp;collector&nbsp;to&nbsp;improve&nbsp;single-binary&nbsp;deployment,
&nbsp;&nbsp;&nbsp;concurrency,&nbsp;resource&nbsp;usage,&nbsp;cross-platform&nbsp;distribution,&nbsp;and&nbsp;ecosystem
&nbsp;&nbsp;&nbsp;integration&nbsp;(cloud-native/edge).

Proposed&nbsp;repository

&nbsp;&nbsp;&nbsp;-&nbsp;Name:&nbsp;apache/hertzbeat-collector-go
&nbsp;&nbsp;&nbsp;-&nbsp;Description:&nbsp;Go-based&nbsp;collector&nbsp;for&nbsp;Apache&nbsp;HertzBeat
&nbsp;&nbsp;&nbsp;-&nbsp;GitHub/GitBox:&nbsp;yes&nbsp;(under&nbsp;github.com/apache,&nbsp;following&nbsp;GitBox
&nbsp;&nbsp;&nbsp;permissions)
&nbsp;&nbsp;&nbsp;-&nbsp;Permissions:&nbsp;all&nbsp;project&nbsp;Committers&nbsp;get&nbsp;write&nbsp;access&nbsp;per&nbsp;GitBox/LDAP
&nbsp;&nbsp;&nbsp;defaults

Scope&nbsp;and&nbsp;boundaries

&nbsp;&nbsp;&nbsp;-&nbsp;Collector-only:&nbsp;protocols&nbsp;plus&nbsp;adapters/plugins;&nbsp;no&nbsp;server/UI&nbsp;code.
&nbsp;&nbsp;&nbsp;-&nbsp;Aim&nbsp;for&nbsp;compatibility&nbsp;with&nbsp;existing&nbsp;metrics/protocols&nbsp;where&nbsp;feasible;
&nbsp;&nbsp;&nbsp;provide&nbsp;migration&nbsp;guidance&nbsp;where&nbsp;needed.
&nbsp;&nbsp;&nbsp;-&nbsp;Initial&nbsp;focus:&nbsp;HTTP/HTTPS,&nbsp;TCP,&nbsp;ICMP&nbsp;Ping,&nbsp;JMX,&nbsp;SNMP,&nbsp;Prometheus
&nbsp;&nbsp;&nbsp;scrape,&nbsp;and&nbsp;several&nbsp;common&nbsp;component&nbsp;adapters.

Maintenance&nbsp;and&nbsp;releases

&nbsp;&nbsp;&nbsp;-&nbsp;Maintainers:&nbsp;HertzBeat&nbsp;PMC/Committers.
&nbsp;&nbsp;&nbsp;-&nbsp;License:&nbsp;Apache&nbsp;License&nbsp;2.0;&nbsp;ensure&nbsp;third-party&nbsp;dependency&nbsp;compliance.

Relationship&nbsp;to&nbsp;existing&nbsp;code

&nbsp;&nbsp;&nbsp;-&nbsp;Independent&nbsp;sub-repo;&nbsp;no&nbsp;impact&nbsp;on&nbsp;existing&nbsp;repositories.&nbsp;We&nbsp;will
&nbsp;&nbsp;&nbsp;document&nbsp;integration&nbsp;and&nbsp;usage.

Process

&nbsp;&nbsp;&nbsp;-&nbsp;This&nbsp;thread&nbsp;runs&nbsp;under&nbsp;lazy&nbsp;consensus&nbsp;for&nbsp;72&nbsp;hours.
&nbsp;&nbsp;&nbsp;-&nbsp;If&nbsp;there&nbsp;are&nbsp;no&nbsp;binding&nbsp;-1&nbsp;votes&nbsp;within&nbsp;72&nbsp;hours,&nbsp;I&nbsp;will&nbsp;open&nbsp;an&nbsp;INFRA
&nbsp;&nbsp;&nbsp;ticket&nbsp;to&nbsp;create&nbsp;the&nbsp;repo&nbsp;and&nbsp;share&nbsp;the&nbsp;link&nbsp;here.

Feedback&nbsp;requested

&nbsp;&nbsp;&nbsp;-&nbsp;Naming&nbsp;preference&nbsp;(hertzbeat-go-collector&nbsp;vs&nbsp;hertzbeat-collector-go)
&nbsp;&nbsp;&nbsp;-&nbsp;Initial&nbsp;scope&nbsp;and&nbsp;priority&nbsp;of&nbsp;adapters/protocols
&nbsp;&nbsp;&nbsp;-&nbsp;Default&nbsp;notifications&nbsp;and&nbsp;merge&nbsp;strategy&nbsp;settings
&nbsp;&nbsp;&nbsp;-&nbsp;Any&nbsp;risks&nbsp;or&nbsp;concerns

Please&nbsp;share&nbsp;your&nbsp;thoughts&nbsp;and&nbsp;your&nbsp;+1/0/-1.&nbsp;Thanks!

Best,&nbsp;Logic

Re: [DISCUSS] Create new repo for Go-based collector: apache/hertzbeat-collector-go (lazy consensus, 72h)

Posted by Chao Gong <go...@apache.org>.
hertzbeat-collector-go +1

Kind regards,
Tom

luo yu <yu...@gmail.com> 于2025年9月1日周一 00:08写道:

> +1
>
> best. shown
>
>
> zhaoqingran <zh...@apache.org> 于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
> >
>

Re: [DISCUSS] Create new repo for Go-based collector: apache/hertzbeat-collector-go (lazy consensus, 72h)

Posted by luo yu <yu...@gmail.com>.
+1

best. shown


zhaoqingran <zh...@apache.org> 于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
>