iNetMon Plus: Complete Guide to Features and Setup

How to Configure iNetMon Plus for Real-Time Alerts

1) Prepare prerequisites

• Install the latest iNetMon Plus build on a machine with network access.
• Account: sign in with an admin account.
• Permissions: ensure the app can access network interfaces and required ports (SNMP/ICMP/agent ports).
• Data sources: identify IP ranges, devices, or services to monitor.

2) Add devices and targets

1. Open Device Management → Add Device.
2. Enter IP/hostname, device type, and optional group/tag.
3. Set credentials (SNMP v2/v3, SSH, WMI) for deeper checks.
4. Save and repeat for all targets.

3) Configure checks and thresholds

1. Go to Monitoring → Checks.
2. Create checks (ping/ICMP, SNMP OID, port TCP/UDP, HTTP(S), custom scripts).
3. For each check, set:
   • Interval (e.g., 30s, 1m).
   • Timeout value.
   • Thresholds for warning/critical (latency %, packet loss, response codes).

4) Set up alert rules

1. Open Alerts → Rules → New Rule.
2. Choose condition(s): specific check failures, threshold breaches, or combination logic.
3. Configure escalation: immediate alert for critical; delayed/warning notifications for transient issues.
4. Add suppression windows (maintenance windows, business hours) to avoid noise.

5) Configure notification channels

• Email: enter SMTP server, sender address, and recipient lists.
• SMS: integrate SMS gateway or third-party provider credentials.
• Push: enable push notifications in user settings and install mobile app if available.
• Webhook/Slack/MS Teams: create and test webhook URLs; map payload fields.
• PagerDuty/ops tools: integrate via API keys for incident management.

6) Customize alert content

• Use templates to include device name, check name, timestamp, metric values, severity, and a troubleshooting hint.
• Add variables/placeholders so alerts are actionable.

7) Test alerts

• Use Test Alert or simulate failures (disable a monitored interface or stop a service) to verify delivery and formatting for each channel.
• Confirm escalation and suppression behave as expected.

8) Tune to reduce noise

• Increase check intervals or add retry counts for flaky links.
• Use grouping and correlated alerts to avoid duplicate notifications for the same outage.
• Implement threshold hysteresis (different values for entering vs. leaving an alert state).

9) Monitor and iterate

• Review alert history and false positives weekly for 2–4 weeks.
• Adjust thresholds, intervals, and notification recipients based on incident impact and frequency.

If you want, I can generate example alert rule definitions, sample webhook payloads, or a step-by-step SMTP setup for your environment.