CoreBit Network Management System – User Guide

CoreBit is a modern network topology and monitoring platform for professional network environments (ISPs, enterprises, and power users).

1. Introduction

CoreBit provides device discovery, live status visibility, topology mapping, and operational monitoring for heterogeneous networks. It is designed to modernize workflows that were historically handled by legacy tooling (e.g., MikroTik “The Dude”), while keeping a clean, scalable approach that fits real-world operations.

Built for
  • ISPs and service providers
  • Enterprise and campus networks
  • Distributed infrastructures and labs
  • Mixed-vendor environments

2. Core Concepts

2.1 Devices

A device is any network-connected entity CoreBit can discover and poll, such as routers, switches, servers, gateways, and virtualization hosts. Devices are identified primarily by IP address, with additional information shown when detected by the selected credential profile.

2.2 Credential Profiles

Credential profiles define how CoreBit accesses and polls devices. Profiles are tested automatically during scans, and the first matching profile is assigned to each discovered device.

Supported profile types
  • SNMP – Generic SNMP-enabled devices
  • Prometheus Node Exporter – Servers exposing node_exporter metrics
  • MikroTik API – MikroTik routers and switches
  • Proxmox API – Proxmox VE hosts

2.3 Maps

Maps are visual representations of your network topology. You can maintain multiple maps for sites, layers, or logical groupings. Devices are placed on a canvas and arranged to match your preferred documentation and operational view.

2.4 Connections

Connections represent relationships between devices on a map. Connections are currently created manually to reflect physical or logical links, uplinks, or site interconnects.

2.5 Monitoring & Status

CoreBit polls devices on a configurable interval and shows availability and performance information where supported by the assigned credential profile.

3. User Interface Overview

3.1 Top Navigation

  • Scan – Discover devices within a CIDR / network range
  • Add Device – Manually register a device
  • Connect – Create manual links between placed devices
  • Logs – View system and event logs
  • Settings – Configure polling, credentials, users, backups, and alert routing

3.2 Device List Panel

The device list shows discovered devices (name and IP), supports search/filtering, and indicates whether a device is already placed on the current map.

3.3 Map Canvas

The canvas is where you build and maintain topology maps. Place devices, arrange them visually, zoom for large environments, and draw connections to document your network.

4. Getting Started

Important: Set up Credential Profiles before running your first scan. Scans rely on these profiles to identify devices and assign the correct polling method.

Step 1: Configure Credential Profiles

  1. Open Settings ? Credential Profiles
  2. Create profiles matching your environment (SNMP, Node Exporter, MikroTik API, Proxmox API)
  3. Save and verify profiles as needed

Step 2: Run a Scan

Scanning is performed in two phases:

  1. Ping sweep across the defined network range (CIDR)
  2. Credential testing against each responding device

When a credential profile matches a device, CoreBit saves the device with that profile and uses it for ongoing polling if the device is added to CoreBit.

Step 3: Place Devices on a Map

  1. Select or create a map
  2. Drag devices from the list onto the canvas
  3. Arrange devices logically (core, distribution, access, edge, sites)

Step 4: Create Connections

  1. Click Connect
  2. Select the source and destination devices
  3. Confirm the connection

5. Device Details

Selecting a device shows key details, depending on the assigned credential profile:

  • Device name and IP address
  • Vendor / OS identification (when available)
  • CPU and memory usage (where supported)
  • Interface/traffic visibility (where supported)
  • Uptime and status indicators

6. Traffic & Performance Monitoring

CoreBit collects performance metrics during each polling cycle. The polling interval is configurable in Settings.

6.1 Monitored Metrics

  • CPU usage
  • Memory usage
  • Interface traffic (RX/TX)
Note: CoreBit currently does not apply alarm thresholds to CPU, memory, or traffic. Alerts are focused on device availability.

6.2 Historical Data

Historical data is currently maintained for up/down states (availability). Performance metrics are shown live and are not stored historically at this stage.

7. Logs, Alerts & Events

7.1 Availability Alerts

CoreBit alerts when devices stop responding to polling and exceed the configured offline threshold. This keeps alerting focused and avoids unnecessary noise.

7.2 Notification Channels

Alerts can be delivered via:

  • Telegram
  • Pushover
  • Webhook endpoints

7.3 On-Duty Scheduling

CoreBit includes an On-Duty system with Day and Night shifts. Users assigned to the active shift receive alerts.

7.4 Logs

The Logs view provides insight into device state changes, scan activity, polling behavior, and system-level events.


8. IP Address Management (IPAM)

CoreBit includes an integrated IP Address Management (IPAM) system that automatically maps all detected IP addresses in your network. IPAM is built directly into discovery and monitoring, ensuring the IP inventory is always accurate and up to date.

8.1 Automatic IP Discovery

During network scans and ongoing polling, CoreBit detects and tracks IP addresses without requiring manual input. As devices are discovered, their IPs are automatically registered and associated with the correct network and device.

8.2 IP Pools & Network Visibility

IP addresses are grouped into address pools based on network ranges. For each pool, CoreBit shows:

  • Total number of IP addresses
  • Assigned IPs
  • Available (free) IPs
  • Offline or unreachable IPs

8.3 Device & Interface Association

When possible, IP addresses are linked directly to the owning device and interface. This makes it easy to trace an IP address back to the exact system and network port using it.

8.4 Always in Sync

Because IPAM is driven by live discovery and polling, the IP inventory stays synchronized with the actual network state. There is no separate database to maintain and no need for external IPAM tools or spreadsheets.   

9. Settings

9.1 Polling & Probing

  • Polling interval
  • Probe timeout
  • Offline threshold (failed probe cycles)
  • Concurrent probe threads

9.2 Advanced Probing Options

  • MikroTik: Keep Connections Open – Maintains persistent MikroTik API connections to reduce false positives
  • Ping Fallback Verification – If API/SNMP fails but ping succeeds, mark device as stale instead of offline (no alarm)

8.3 Credential Profiles

Create reusable profiles for your network devices. Profiles are automatically tested during scan and saved per device when matched.

8.4 Notifications

Configure notification endpoints used for device status alerts (Telegram / Pushover / Webhook). Combine this with the On-Duty system to route alerts to the right operators.

8.5 Backup & Restore

CoreBit supports manual and scheduled backups with retention policy. Backups can be restored directly from the settings interface.

9.6 User Management

CoreBit is a multi-user system with three access levels:

  • Administrator – Full access, including settings
  • Superuser – Operational access, no access to Settings
  • Viewer – Read-only access

10. Target Audience & Use Cases

CoreBit is designed for:

  • Network administrators
  • ISPs and service providers
  • Enterprise networks
  • Power users and homelabs
Typical use cases
  • Backbone and aggregation visibility
  • Topology documentation as living maps
  • Operational availability monitoring
  • Team-based monitoring with On-Duty alert routing

11. Best Practices

  • Configure Credential Profiles before scanning
  • Use one map per site, role, or logical layer
  • Keep device naming consistent
  • Tune concurrent probe threads to avoid mass probe failures
  • Use the On-Duty system to prevent alert fatigue
  • Treat maps as living documentation and keep them updated

12. Support & Feedback

CoreBit is actively developed. If you have feature requests, integration needs, or want to share feedback from production usage, please contact the CoreBit team.

CoreBit – Clear insight into the core of your network.