elastic / elastic/beats

[Heartbeat/Synthetics] Network Discovery Functionality

Open
#38,145 4 comments 2 reactions 0 assignees View on GitHub
enhancement Stalled Team:obs-ds-hosted-services
Dominant language
Go
Stars
12.7k
Forks
5k
Avg merge
2d 15m
Merged PRs (30d)
385

Description

**Describe the enhancement:**
I would like Heartbeat can be able to scan a network, determine hosts/ip, and report back hosts' ICMP status, up and down.
Think NMAP but built-in. It can be run on specified intervals just like how we currently create monitors. The current way we can "scan" is by manually inputting ICMP monitors. This has become a hassle and super tedious.

**Describe a specific use case for the enhancement or feature:**
Our team has used other competitor's monitoring tools and they offer network discovery. It's an important thing for being able to quickly determine if a host is pingable or not.

Contributor guide

Open the contributing guide

Research direction

Start with Heartbeat/Synthetics and the existing ICMP monitor flow to understand how monitors are configured and scheduled. The issue names no files or tests, so first locate those entry points and clarify the network-scan scope. Done would mean scanning a specified network at intervals and reporting discovered hosts with ICMP up or down status.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking, observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.