fti-sfuke opened a new issue, #3937:
URL: https://github.com/apache/hertzbeat/issues/3937

   ### Feature Request
   
   
   ## **Feature Request**
   
   ### A concise description of the feature
   
   Currently, when adding a Debian Linux node as an **agentless SSH monitor**, 
HertzBeat requires a **static IP address**.
   I would like to request support for using **hostname-based resolution (DNS 
or mDNS, e.g. `node-name.local`)** instead of only IP-based configuration.
   
   <img width="1917" height="958" alt="Image" 
src="https://github.com/user-attachments/assets/9d4f221e-18cf-496b-8220-6e5cfd142338";
 />
   
   This would allow monitoring to continue seamlessly even when the node’s IP 
address changes.
   
   ---
   
   ## **Is your feature request related to a problem? Please describe**
   
   Yes.
   
   In our environment:
   
   * Debian Linux nodes are added as **agentless SSH clients**
   * Some nodes receive **dynamic IPs via DHCP**
   * When the IP changes, HertzBeat marks the node as **DOWN**, even though the 
machine is still online and reachable via hostname
   
   This causes:
   
   * False “node offline” alerts
   * Manual reconfiguration whenever IPs change
   
   Using **hostname or mDNS-based SSH monitoring** would solve this issue.
   
   ---
   
   ## **Additional Context / Use Case**
   
   * Environment: Debian Linux (agentless SSH)
   * Monitoring type: OS / CPU / Memory / Disk
   * Network: DHCP-based, IPs may change
   * Hostnames are resolvable via:
   
     * mDNS (`*.local`)
     * or internal DNS
   
   **Example use case:**
   
   ```text
   node-01.local → IP changes → monitoring should continue without interruption
   ```
   ---
   
   ### Is your feature request related to a problem? Please describe
   
   ## **Expected Behavior**
   
   * Allow SSH monitoring configuration using:
   
     * Hostname (DNS)
     * mDNS hostname (`.local`)
   * HertzBeat should resolve the hostname dynamically before each check
   * Node should not be marked DOWN solely due to IP change
   
   ---
   
   ## **Alternatives / Questions**
   
   If this feature is not currently supported, guidance on **best practices** 
would also be very helpful, such as:
   
   * Recommended DNS/DHCP setup
   * Any workaround for dynamic IP environments
   
   ---
   
   ## **Appreciation**
   
   Thank you to the HertzBeat maintainers and contributors for building such a 
**powerful, clean, and user-friendly monitoring platform**.
   It has been extremely useful for our production and edge environments 🙏
   
   <img width="1919" height="881" alt="Image" 
src="https://github.com/user-attachments/assets/653d5bb0-70c5-4135-a2be-023368c26915";
 />
   
   ---
   
   ### Describe the solution you'd like
   
   _No response_
   
   ### Describe alternatives you've considered
   
   _No response_
   
   ### Additional context
   
   _No response_


-- 
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]

Reply via email to