This is an automated email from the ASF dual-hosted git repository.
duansg pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hertzbeat.git
The following commit(s) were added to refs/heads/master by this push:
new d0f6a04661 [docs] Add new committer blog (#3894)
d0f6a04661 is described below
commit d0f6a046617335538dcfc8ac5d74ccd0c870c6b0
Author: DeleiGuo <[email protected]>
AuthorDate: Tue Dec 9 09:46:19 2025 +0800
[docs] Add new committer blog (#3894)
---
home/blog/2025-12-07-new-committer.md | 52 ++++++++++++++++++++++
.../2025-12-07-new-committer.md | 51 +++++++++++++++++++++
home/src/pages/team/data/member.json | 5 +++
3 files changed, 108 insertions(+)
diff --git a/home/blog/2025-12-07-new-committer.md
b/home/blog/2025-12-07-new-committer.md
new file mode 100644
index 0000000000..0ed3d237c2
--- /dev/null
+++ b/home/blog/2025-12-07-new-committer.md
@@ -0,0 +1,52 @@
+---
+title: Welcome HertzBeat's New Community Committer!
+author: Delei
+author_title: ZiQiu Guo
+author_url: https://github.com/delei
+tags: [opensource, practice]
+keywords:
+ [
+ open source monitoring system,
+ alerting system,
+ Apache,
+ Apache Committer,
+ HertzBeat,
+ ]
+---
+
+> Hello everyone, it's a great honor to be invited by the community to become
Apache HertzBeat Committer.
+
+## Self-Introduction
+
+Since starting my career, I have mainly been engaged in backend development
work and have a great interest in open-source projects. I am currently employed
at a financial software company and also undertake the management work of
operation and maintenance.
+
+## First Encounter Apache HertzBeat
+
+In our actual work, we have been using the monitoring system consisting of
Prometheus and Grafana. As the number of devices and services to be monitored
increased, and due to the limited number of operation and maintenance
personnel, the workload for daily configuration and maintenance rose sharply,
making it impossible for us to promptly handle and respond to user feedback.
+At this point, we have been constantly looking for a lightweight open-source
monitoring system. Apache HertzBeat is ready to use out of the box, has
comprehensive functions, does not require an agent, is compatible with
Prometheus, and fully covers all the protocols we currently use. Therefore, we
quickly set it up and put it into use based on Docker internally.
+
+As an open-source enthusiast myself, I encountered a few minor issues after
using the software for some time. Since it happened to be written in a
programming language I'm proficient in, I delved into the source code,
endeavoured to refine the implementation, and contributed my improvements back
to the community.
+
+## The Path to Open Source Contributions
+
+I initially began using the tagging feature, only to discover right away that
tag maintenance had an NPE issue. So I delved into the source code and gained a
preliminary understanding of the cause. Following the official documentation, I
submitted [issue#3605](https://github.com/apache/hertzbeat/issues/3605) and
created my first pull request to address it. Though a minor change, it was
merged promptly, which proved immensely encouraging.
+
+During subsequent, more in-depth usage, based on the actual monitored devices
and scenarios, I primarily added several new monitoring services, such as
[Apache DolphinScheduler](https://github.com/apache/hertzbeat/pull/3656),
[MacOS](https://github.com/apache/hertzbeat/pull/3715), [Synology
NAS](https://github.com/apache/hertzbeat/pull/3721), amongst others.
Collaborating with other community contributors, I refined and resolved the
`jexl` keyword issue while also enhancing the status pa [...]
+
+## Community Engagement and Growth
+
+Through daily contributions to Apache HertzBeat, I have also learnt how to
collaborate more effectively within open-source projects. Communicating and
working alongside community members has given me a deeper appreciation for the
unique appeal of the ‘Apache Way’ and the spirit of open-source.
+
+Becoming a Committer entails greater responsibility. Beyond continuing to
contribute, it is vital to maintain a rigorous approach, offering constructive
feedback and recognition to contributors, thereby helping more individuals
participate in the community and grow within it.
+
+## Advice for Open Source Developers
+
+For developers who are new to open source, first of all, please be brave to
try and let go of your worries to take the first step. The process of making
contributions requires time, but as long as you have patience, you will achieve
results.
+
+In the Apache HertzBeat community, by communicating more, many enthusiastic
and friendly open-source contributors in the community can collaborate
together. We can first gradually use and experience the functions, and start to
attempt to contribute. For example, small contributions such as correcting
spelling errors in the documentation and fixing incorrect comments, and then
gradually deepen our understanding of the source code and try to fix the
problems.
+
+## Conclusion
+
+My heartfelt thanks to all community partners for your patient reviews and
thoughtful guidance. It has been a tremendous privilege to witness Apache
HertzBeat successfully graduate to a TLP project during this period.
+
+Becoming a Committer marks merely a small milestone for me. I look forward to
continuing to uphold the spirit of open source alongside Apache HertzBeat,
attracting more outstanding developers to jointly build a technologically
advanced and vibrant community.
diff --git
a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2025-12-07-new-committer.md
b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2025-12-07-new-committer.md
new file mode 100644
index 0000000000..299ce0065d
--- /dev/null
+++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2025-12-07-new-committer.md
@@ -0,0 +1,51 @@
+---
+title: 热烈欢迎 HertzBeat 小伙伴新晋社区 Committer!
+author: Delei
+author_title: ZiQiu Guo
+author_url: https://github.com/delei
+tags: [opensource, practice]
+keywords:
+ [
+ open source monitoring system,
+ alerting system,
+ Apache,
+ Apache Committer,
+ HertzBeat,
+ ]
+---
+
+> 大家好，非常荣幸收到社区邀请，成为 Apache HertzBeat™ Committer。
+
+## 个人介绍
+
+自从事工作以来，我一直主要从事后端研发工作，对开源项目有非常大的兴趣。目前主要在一家金融软件公司就职并兼职运维管理工作。
+
+## 初识 Apache HertzBeat
+
+在实际工作中，我们之前一直在使用 Prometheus + Grafana
这一套监控系统。随着所需监控的设备和服务越来越多，由于运维人员有限，对于日常配置和维护工作量的急剧增加，使得我们无法及时处理和响应用户的反馈。此时我们一直想寻找一款轻量级开源监控系统，Apache
HertzBeat 开箱即用、功能全面，无需 Agent，兼容 Prometheus，且全面覆盖目前我们使用的各类协议。于是我们内部基于 Docker
快速搭建并投入使用。
+
+我本身就是一名开源爱好者，在实际使用了一段时间后发现了一些小的问题，由于刚好是我擅长的开发语言，于是便开始深入源码，尝试完善代码并贡献给社区。
+
+## 开源贡献之路
+
+我最初开始使用的是标签功能，结果一开始就发现标签维护有 NPE 问题。于是便研究了下源码，初步了解了问题原因。于是我通过官网的指引，提交了
[issue#3605](https://github.com/apache/hertzbeat/issues/3605),并提交了第一个 PR
来修复。虽然是一个很小的改动，但很快就被合并了，这给予了我极大的鼓励。
+
+在接下来更加深入的使用过程中，根据实际监控的设备和场景，我主要增加了一些新的监控服务，比如 [Apache
DolphinScheduler](https://github.com/apache/hertzbeat/pull/3656)、[MacOS](https://github.com/apache/hertzbeat/pull/3715)、[Synology
NAS](https://github.com/apache/hertzbeat/pull/3721) 等，并和其他社区贡献者一起完善和修复了 `jexl`
关键字问题，也对状态页功能做了进一步的增强等。
+
+## 社区参与和成长
+
+通过参与 Apache HertzBeat 的日常贡献，也学习到如何更高效地在开源项目中协作。与社区成员的沟通与协作，让我更加深刻地体会到 "Apache
Way" 的独特魅力和开源精神。
+
+成为 Committer
意味着肩负更多责任。除了继续参与贡献外，更重要的是保持严谨的态度，给予贡献者建设性的反馈与认可，帮助更多人参与社区并在社区中收获成长。
+
+## 给开源开发者的建议
+
+对于初次参与开源的开发者来说，首先请勇于尝试，放下包袱走出第一步。贡献的过程，需要时间，但只要有耐心，就会有成果。
+
+在 Apache HertzBeat
社区中，多沟通交流，社区中很多热情和友善的开源贡献者可以一起开源协作。我们可以先逐步使用和体验功能，并开始尝试贡献。例如文档错别字，错误注释等小的贡献，然后逐步深入理解源码，并尝试修复问题。
+
+## 结语
+
+衷心感谢各位社区伙伴的耐心 Review 和悉心指导。非常有幸在这段时间内，见证了 Apache HertzBeat 成功毕业成为 TLP 项目。
+
+成为 Committer 只是我一个小的里程碑，期望和 Apache HertzBeat
一起继续秉持开源精神，吸引更多优秀的开发者，共同打造一个技术领先且充满活力的社区。
diff --git a/home/src/pages/team/data/member.json
b/home/src/pages/team/data/member.json
index d49b16c3a7..9577bf9f6e 100644
--- a/home/src/pages/team/data/member.json
+++ b/home/src/pages/team/data/member.json
@@ -146,6 +146,11 @@
"githubId": "112607719",
"gitUrl": "https://github.com/Duansg";,
"name": "Duansg"
+ },
+ {
+ "githubId": "17263766",
+ "gitUrl": "https://github.com/delei";,
+ "name": "Delei"
}
]
}
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
