Applications

Applications is a single, host-by-host view of every open port and running service GridNMS has found on your network — across both your managed devices and the unmanaged hosts network discovery has found. It answers “what’s actually running out there?” without you having to open each device one at a time.

Where to find it

Open Explore → Applications.

At the top, four summary cards give you running totals: Devices and Hosts (how many of each kind of machine have something open), Open ports, and Unique applications.

The application list

Each row is one host:

Column	Description
Host	The device or host’s name.
Type	Device for something in your managed inventory, Host for an unmanaged, discovered-only machine.
Address	Its IP address.
Class	The device class, for managed devices.
Open Ports	A badge per open port, colored by category (web, database, management, mail, network, file) and labeled with the port number and, where known, the application’s name.
Last Scanned	When one of its ports was most recently seen open.

Use the search box to filter by device or host name, the device picker to narrow to one device, and the port/service filter to find hosts running a specific port number or application name.

Banners

Some port badges carry a small banner tag next to them — raw text the service itself returned during a scan (an SSH version string, for example, or an HTTP server header). Click it to see the full captured text, any HTTP headers that came with it, and when it was captured. A banner is a point-in-time snapshot, not a live status, so one that hasn’t been refreshed in a while is shown in a muted style with its age called out. Most services won’t have a banner yet — that’s expected, not a sign anything is wrong.

Adding an unmanaged host as a device

Any row marked Host (rather than Device) is an unmanaged machine discovery has found — it isn’t in your inventory and nothing is actively monitoring it yet. Click Add as device on its row to bring it in:

1. Confirm or edit the name GridNMS suggests, and pick a class.
2. Choose which of its discovered ports to turn into active monitors — well-known ports (like HTTP, HTTPS, DNS, or SMTP) are pre-checked for you; anything else starts unchecked so promoting a busy host doesn’t create a monitor for every port at once. A UDP-based port is checked with a best-effort probe, since a silent UDP service can’t be proven down the way a TCP one can.
3. Click Add device. GridNMS creates the device, enables the monitors you picked, and opens its new detail page.

The device then behaves like any other in your inventory — see Devices & Inventory for what happens next, including adding credentials so it reports full metrics.

Where to go next

• See the raw host list these applications are drawn from in Hosts.
• Find more hosts and applications with Network Discovery.
• Model a business service out of what you find here, with dependencies and rolled-up health, in Service Monitoring.
• Trace a device’s exposed applications on the network map in Graph Explorer.