Top 10 Tips for Monitoring with DEKSI Network Monitor
1. Map your network first
Scan and generate an automatic network map so devices, dependencies, and groups are visible before adding monitors.
2. Use appropriate checks per device
Match check types to assets: ICMP/TCP for availability, SNMP/WMI for device metrics, HTTP/HTTPS for web services, and service/process checks for servers.
3. Set realistic thresholds and RTT limits
Configure round-trip time and resource thresholds based on baseline measurements to reduce false positives.
4. Group devices and apply templates
Organize hosts into logical groups and use monitoring templates (ports, SNMP OIDs, services) to ensure consistent checks and faster deployment.
5. Configure multi-channel alerts
Enable multiple alert actions (screen messages, email, SMS, sound, run program, log entry) and prioritize channels by severity.
6. Use automated remediation actions
Attach actions like restarting services, running scripts, or rebooting machines to critical alerts to reduce manual intervention.
7. Monitor historical performance
Collect and review historical CPU, disk, traffic, and RTT graphs to spot trends and plan capacity upgrades.
8. Verify notification escalation
Test alert delivery and set escalation rules so unresolved incidents escalate to the next on-call person or channel.
9. Secure access and remote controls
Restrict DEKSI administrative access, use least-privilege accounts for remote commands (reboot/service control), and log all remote actions.
10. Regularly review and tune monitors
Schedule periodic audits to remove stale checks, refine thresholds, add new assets, and update templates after infrastructure changes.
Leave a Reply