apache / apache/hertzbeat

[Question] Questions about Metrics Collection Architecture

Open
#3,221 8 comments 3 reactions 0 assignees View on GitHub
question
Dominant language
Java
Stars
7.4k
Forks
1.3k
Avg merge
1d 20h
Merged PRs (30d)
32

Description

### Question

I am curious about a few points related to the system architecture:
- Collectors can be scaled up easily, but what about the manager?
- If not, is there any plan to improve or change the architecture to better support horizontal scaling in the future?

- Is there a specific reason for using a persistent custom TCP protocol between the manager and collectors?
- Was using HTTP APIs considered but rejected due to performance or efficiency concerns?

Just wanted to understand the reasoning behind these choices and whether any future improvements are being planned in these areas.

Thanks in advance!

Contributor guide

Open the contributing guide

Research direction

Start by reading the manager and collector architecture, focusing on how the persistent custom TCP protocol connects them and how HTTP APIs compare. Determine whether the project documents manager scaling, protocol rationale, or future architecture plans; done means providing or updating that explanation with the issue's questions answered.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems, networking, observability
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.