Network discovery
Network discovery lets an Advanced agent inventory the private network it runs in: which hosts answer, which ports are open, which services they expose. From the results, you create Ping, Port, Certificate and HTTP sensors in a few clicks.
Requirements
An Advanced agent (Enterprise plans), version 1.5 or later, and the User role.
Start a discovery#
- Open the agent in Configuration → Agents, then its Discovery tab.
- Click Start discovery and choose:
- Auto-detect network — the agent scans the network of its main interface (the one with a gateway).
- Specific network (CIDR)… — enter a range such as
10.20.0.0/24, for an agent that reaches several networks.
- Wait for the scan to end: the page shows it in progress. Only one discovery runs per agent at a time.
The scan only reads: the agent pings the addresses of the range, tries to open a connection on 52 common ports of each host that answers, and looks up host names (reverse DNS). It changes nothing on your network, but it may be noticed by intrusion detection systems: warn your security team first. Only IPv4 networks are scanned.
Read the results#

Discovered hosts lists each host that answered, with its address, name when known, and open ports with the service usually found on them (ssh, postgresql, http…). For each one, Onagre suggests sensors:
| Suggested sensor | When | Schedule |
|---|---|---|
| Ping | for each host | every 5 minutes |
| Port | for each open port | every 5 minutes |
| Certificate (port 443, alert 30 days before expiry) | when port 443 is open | daily at 06:00 |
HTTP (GET, accepts 200, 301 and 302) |
when a web port is open | every 5 minutes |
Create the sensors#
- Select the sensors to create, one by one or with Select all.
- Click Create selected resources.
The sensors are created on this agent, named after the address (10.20.0.12, 10.20.0.12:5432, https://10.20.0.12…), with a 1.5-second timeout, Major severity and the tag discovered — search tag:discovered in Resources to find them. They are placed in your default service and environment.
Set up alerting
The created sensors only alert your own mobile app, if you registered one. Select them in Resources and use Alertings to choose the integrations to notify, then move them to the right service.
The discovery is then archived.
Discovery history#
Discovery history, at the bottom of the tab, lists past discoveries: who requested them, when they were requested and completed, and how long they took.
Ports scanned#
| Family | Ports |
|---|---|
| Web | 80, 443, 5000, 8000, 8008, 8009, 8080, 8081, 8088, 8090, 8091, 8443, 8888, 9000 |
| Databases | 1433 (SQL Server), 1521 and 2483 (Oracle), 3306 (MySQL/MariaDB), 5432 (PostgreSQL), 6379 (Redis), 9042 (Cassandra), 9200 (Elasticsearch), 27017 (MongoDB), 4444 and 4567 (Galera cluster) |
| Messaging | 2181 (ZooKeeper), 5672 (RabbitMQ), 9092 (Kafka) |
| Remote access and system | 21 (FTP), 22 (SSH), 25 (SMTP), 53 (DNS), 110 (POP3), 143 (IMAP), 445 (SMB), 2049 (NFS), 3389 (RDP), 5900 (VNC), 5985 and 5986 (WinRM) |
| Platforms and tools | 2082, 2083 (cPanel), 2375, 2376 (Docker), 3000 (Grafana), 5601 (Kibana), 6443 (Kubernetes API), 7001, 7002 (WebLogic), 8200 (Vault), 9100 (Node Exporter), 9418 (Git) |