# IPNetwork Monitor > - [Monitoring Tool You Can Trust: Feature Overview | IPNetwork Monitor](https://ipnetwork-monitor.com/features/): Simplify Network Management with Our Powerful Features IPNetwork Monitor enables you to monitor both Windows and Unix-based networks, a variety of servers, and network equipment. It also tracks the performance and availability of web applications and other applications. Our advanced alerting system provides timely notifications through various channels, including email, SMS, and instant messengers. The ### Monitoring Tool You Can Trust: Feature Overview #### Simplify Network Management with Our Powerful Features #### Try IPNetwork Monitor for Free ✕ Monitoring Tool You Can Trust: Feature Overview Simplify Network Management with Our Powerful Features IPNetwork Monitor enables you to monitor both Windows and Unix-based networks, a variety of servers, and network equipment. It also tracks the performance and availability of web applications and other applications. Our advanced alerting system provides timely notifications through various channels, including email, SMS, and instant messengers. The system can also execute corrective actions locally or remotely via SSH. Reporting and graphs are accessible through a user-friendly web interface. IPNetwork Monitor supports over 20 monitoring methods and more than 10 alerting technologies. Customizable monitors and alerts allow you to tailor your monitoring system to meet your evolving business needs. Application templates simplify the process of setting up monitoring. With just a few clicks, you can deploy a complete set of monitors for a host. An application template is a preconfigured set of monitors designed to check specific applications or services (e.g., MS Exchange) or entire servers (like web or mail servers). IPNetwork Monitor comes with over 50 predefined application templates and provides tools to create your own. IPNetwork Monitor includes an add-on product for comprehensive monitoring of web applications and e-commerce websites: Web Transaction Monitor . This tool simulates the actions of a real user interacting with a web application or e-commerce site. SMS alerts via GSM modem/phone allow you to send SMS messages through a GSM modem or phone connected to your computer. This is a highly reliable method for receiving notifications about system failures or significant performance degradation. IPNetwork Monitor is available in several editions: Basic, Professional, and Enterprise. The Basic edition offers a limited set of features and supports up to 200 monitors. The Professional edition is available with either 500 or 1000 monitors. The Professional 1000 edition includes 5 Remote Network Agents . The Enterprise edition provides unlimited monitors and agents. Below, you’ll find detailed information about IPNetwork Monitor’s key features. --- - [Getting started with IPNetwork Monitor | IPNetwork Monitor](https://ipnetwork-monitor.com/gettingstarted/): Getting Started with IPNetwork Monitor Table of Contents Product Overview System Requirements Quick Start: Monitor a Small Network Recommended Settings Security Considerations Using Backups Common Pitfalls Troubleshooting This page provides essential information on using IPNetwork Monitor. Note: as IPNetwork Monitor is a general-purpose monitoring application, there may be several setup and usage scenarios. We provide ### Getting started with IPNetwork Monitor #### Getting Started with IPNetwork Monitor ##### Product Overview ##### System Requirements ##### Quick Start: Monitor a Small Network ##### Recommended Settings ##### Security Considerations ##### Using Backups ##### Common Pitfalls ##### Troubleshooting #### Try IPNetwork Monitor for Free ✕ Getting started with IPNetwork Monitor Getting Started with IPNetwork Monitor Table of Contents Product Overview System Requirements Quick Start: Monitor a Small Network Recommended Settings Security Considerations Using Backups Common Pitfalls Troubleshooting This page provides essential information on using IPNetwork Monitor. Note: as IPNetwork Monitor is a general-purpose monitoring application, there may be several setup and usage scenarios. We provide a typical quick start sequence below. Product Overview IPNetwork Monitor is a Windows application capable of monitoring various network devices and alerting to changes in performance and/or availability. IPNetwork Monitor allows you to organize continuous monitoring of your critical network assets: servers, applications, and network equipment. Supported monitoring methods include: SNMP v1/v2c/v3; SNMP traps , payload can be validated (match against a regular expression); WMI (Windows Management Instrumentation) queries , including resource utilization (CPU, memory, processes, etc.) and custom queries; Web sites and services monitoring – HTTP/HTTPS GET and POST requests including response validation, FTP; Web transaction monitor (WTM) – for complex multi-step monitoring scenarios of using sites and Web applications; DNS: check whether the DNS server works and allows validation of its response; can also detect DNS zone updates; database servers – Oracle, MySQL, and MSSQL Server, others via ODBC; mail servers – SMTP including actual sending of a test e-mail message, POP3, IMAP; email round-trip – sends an email via SMTP, then checks its delivery on POP3 or IMAP server; file size, disk space, Windows service availability; basic connectivity checks – PING, TCP connect , UDP datagram send/receive ; run a script or program, including Nagios plugins and Python scripts; run a script on a remote computer via SSH; collecting resource usage metrics via SSH; traffic monitoring via SNMP and WMI (average speed and data volume for a specified time interval). virtual machines (hosts and guests metrics), supported are Hyper-V, VMWare, KVM, and XenServer (the latter two – via application templates) office applications, such as Microsoft SharePoint, MS Exchange (via application templates) Application monitoring templates offer a great number of monitor presets to cover many typical use cases; users can also create their own templates. More than 50 server and application monitoring templates are provided. You can configure IPNetwork Monitor to alert you if a given monitor enters a problem state (performance or availability issue). The following simple actions are available: send e-mail (a number of template variables can be used; email text and recipients list can be completely customized); send SMS (short message) via GSM phone/modem or email; set SNMP variable value; play sound (both in the web interface and monitoring service); execute a program (for automatic problem resolving) or Python script; execute a script on a remote computer via SSH; send HTTP(S) request (this allows posting notifications to a variety of messaging services, such as Slack, HipChat, Stride, Microsoft Teams, etc.); show pop-up message; send network message via Net Send; send message to instant messenger (Jabber). Every simple action can have its own schedule; alerts can include an arbitrary number of simple actions, thus providing a very flexible way of reacting to monitoring events. System Requirements Note that the requirements below assume all your monitors are being polled once a minute, you retain monitoring data for 180 days (half a year), and keep at least 3 backup copies of your monitoring database. The actual resources amount will differ; values below are shown to provide you with a starting point to assess your needs. Minimal License Monitors Number RAM Recommended (Gb) Minimal CPU Speed (GHz) Database Size (Gb) Backups Disk Usage (Gb) Freeware 50 0.75 0.8 0.1 0.15 Basic 200 200 1.0 1 0.25 0.3 Professional 500 500 2.0 1.5 0.7 0.8 Professional 1000 1000 3.0 2 1.4 1.6 Enterprise 2500 4.0 2.5 3.5 4.0 ( * ) Note: you need at least twice the database size amount of free disk space to generate a backup. ( ** ) If two or more CPU cores are available, IPNetwork Monitor overall performance increases. Quick Start: Monitor a Small Network A typical small network consists of several computers running typical services (mail server, DNS server, domain controller, file server, etc.), along with workplace computers, all included in a single local network. Since all the network devices are within a single network, there’s usually no need to install remote network agents. Simple network discovery can be sufficient to detect all the vital network devices and set up a basic set of monitors. Please read the Quick Start: Monitor a Small Network page for detailed instructions on this scenario. Recommended Settings Default settings IPNetwork Monitor is installed with match most setups. While monitoring setup spans over a few hosts and doesn’t require much system resources, default settings work fine. As the monitoring setup grows, keeping it efficient and easy to manage may become a challenge. It is recommended to address possible growth issues by setting up monitoring properly: take into account possible situations and simplify maintenance tasks. This could be achieved by: avoiding unique, individual settings allocating enough resources providing failover notification means making sure the monitoring setup health is itself monitored Please read more about this on the recommended settings page. Security Considerations Monitoring deals with sensitive data: both hosts and monitors settings may contain information not intended for public access. Apart from that, IPNetwork Monitor is built from several software components; security issues may be found associated with those components. Keeping the installation up-to-date, from a security viewpoint, is important. Note that information security isn’t a one-time task. It’s both a process and a discipline; if certain habits are developed to address current and possible risks, keeping your system secure becomes a simpler task. In short, security-related recommendations can be briefly explained as: keep everything up-to-date and properly upgraded utilize “least access possible” approach avoid using defaults: check and update settings as recommended by security experts assume nothing: when incorporating a new element into monitoring (say, running an external program), manage it as a possible security threat Read more about this on the Security Considerations page. Using Backups Monitoring everything important; keeping all the devices and services well-configured and up-to-date; making backup copies – these three activities are fundamental for every IT infrastructure. Recent IPNetwork Monitor versions all have built-in tools for database maintenance. Monitoring configuration, gathered performance data, reports – all these data pieces are kept within the IPNetwork Monitor monitoring database. Unless one cares about creating backup copies of monitoring data, they will be damaged or altogether lost; it’s only a matter of time. The following guidelines can help you understand whether you would need to back up your monitoring data: it only takes a few mouse clicks to request a manual backup creation; it usually takes 2-3 minutes to have the backup complete it can take hours to process and fix a damaged database (imagine hardware failures; blackouts; security incidents; OS or other software failures causing the system to hang), and some data still can be irreversibly lost keeping backups on the same storage device where the database itself is located can result in total data loss if the corresponding storage device fails testing backups (by restoring them) only takes a few minutes more, but it confirms the backup is valid and can be relied upon For more details on the above, please read the Using Backups page. Common Pitfalls Whereas default IPNetwork Monitor settings do work fine for small monitoring setups, as more monitors are added, care should be taken to avoid certain configuration mistakes. Every monitor’s poll can result in quite a number of actions. While there are few monitors, the impact of that can be negligible. As the number of monitors and/or frequency of polling grows, that can easily become the bottleneck. The following is the list of most frequent configuration flaws: utilizing too much resources by polling monitors too frequently, or doing discovery on large networks over all known ports using no password to restrict access to the GUI client and/or Web interface running monitoring on busy systems making no backup copies of the monitoring database and/or custom Web interface pages While every effort was made to make IPNetwork Monitor work as efficiently as possible, while staying as error-proof as possible, we still recommend to optimize IPNetwork Monitor installation for performance at first opportunity. Read more about typical user errors on the Common Pitfalls page. Troubleshooting In case IPNetwork Monitor doesn’t work as expected or breaks, please follow the below shortlist to have the problem handled as fast as possible: send us IPNetwork Monitor version (“Help > About IPNetwork Monitor…”), OS type, version, and build number (run “winver” command) send us IPNetwork Monitor logs (compress the entire C:\ProgramData\IPNetwork Monitor\logs folder and send us the resulting archive) explain us in most detail the issue (what was done, what happened, what was expected instead) send us all screenshots (namely, those of error messages, Logs view, affected monitor’s parameters (Main parameters, State conditions, Alerting tabs) contact us via means on the support page Read more about handling monitoring problems on the Troubleshooting page. --- ## Comparison - [IPNetwork Monitor vs Datadog | IPNetwork Monitor](https://ipnetwork-monitor.com/comparison/ipnm-vs-datadog/): Criteria IPNetwork Monitor Datadog Platform On-premises Windows-based monitoring with unified desktop & web UI. Requires several separate components to achieve full-stack visibility. Agents Remote Network Agent for distributed networks. Dependence on numerous agents adds setup and maintenance complexity. Pricing Simple per-monitor licensing with a free 50-monitor tier. Module-based pricing can result in unexpected overage charges. ### IPNetwork Monitor vs Datadog #### Choose IPNetwork Monitor for simpler, more complete network monitoring #### Trusted by teams—see why they choose IPNetwork Monitor ##### Accelerated time to value ##### Local-first security ##### All-in-one monitoring #### Frequently Asked Questions about IPNetwork Monitor vs Datadog ##### IPNetwork Monitor is 100% SELF-HOSTED #### IPNetwork Monitor vs. other monitoring tools #### Try IPNetwork Monitor for Free ✕ IPNetwork Monitor vs Datadog See how IPNetwork Monitor compares on setup, pricing, scalability, alerting, dashboards, and more. Try IPNetwork Monitor Criteria IPNetwork Monitor Datadog Platform On-premises Windows-based monitoring with unified desktop & web UI. Requires several separate components to achieve full-stack visibility. Agents Remote Network Agent for distributed networks. Dependence on numerous agents adds setup and maintenance complexity. Pricing Simple per-monitor licensing with a free 50-monitor tier. Module-based pricing can result in unexpected overage charges. Scalability Scales from small sites to distributed networks via agents. Host-based licensing grows costly as environments scale. Integrations Open protocols (SNMP, WMI, syslog, SSH, HTTP/S, ODBC) and custom scripts instead of heavy proprietary plug-ins. Many integrations depend on additional add-ons or modules. Alerts Flexible alert rules with multiple delivery and script actions. Does not provide built-in AI-driven root-cause analysis. Visibility Full-stack view from basic uptime to traffic, databases, system resources and synthetic web transactions. Application-centric focus with limited coverage of hybrid infrastructure. Dashboards Clear status views in desktop and web consoles. Often needs intricate custom dashboards to expose key insights. Logs / Search Central event log and monitor logs with time-range filters, state change history and sortable web reports. Log correlation is largely manual, increasing operational overhead. Adoption / Training Quick Start guides, discovery wizards and application templates make initial setup fast even for small teams. Typically requires formal training and dedicated staff time. Monitoring 40+ monitor types covering network devices, Windows/Linux servers, databases, web apps, traffic, syslog and more. Agent-heavy design can consume substantial system resources. Deployment Installs on Windows with optional remote agents and a built-in web UI – no external database or SaaS tenancy required. Configuration can be complex, resource-intensive and time-consuming. Retention Flexible history retention for reports and analysis. Extended data retention usually demands higher-tier subscriptions. Analytics Built-in graphs, trend analysis and issue reports provide practical performance analytics without extra modules. In-depth traffic analytics often rely on complementary third-party tools. Distribution Remote Network Agents enable secure monitoring of remote subnets, including those without Windows hosts. Full APM capabilities are reserved for premium, top-tier plans. Experience Single monitoring server with integrated Windows and web interfaces, reports and admin tools in one place. SaaS-only interface split across multiple views and consoles, giving a less unified experience. Value Rich monitoring, alerting and reporting at SMB-friendly pricing plus a perpetual free tier for smaller environments. Premium pricing oriented toward larger enterprises, with costs rising as data volume and host count grow. Support Email support with comprehensive documentation. Support offerings prioritize enterprise tiers, with faster response times tied to higher-priced plans. Noise reduction Monitor dependencies and state conditions reduce alert storms. High alert volumes can require extensive manual tuning to control noise. Security Supports protocols like SNMP v3, SSH and HTTPS plus syslog and Windows Event Log monitoring for security-relevant events. Security depends on shared SaaS infrastructure and internet access, with credentials and data stored in vendor-hosted systems. API Support HTTP/SSH integrations; MCP API coming next release. Powerful APIs are available but meaningful automation typically requires engineering effort and custom scripting. Sensitive Data Protection On-premises solution storing all credentials and configuration data locally in a secure RDBMS under full user control. Cloud-hosted service where configuration, metadata and telemetry reside outside the customer’s own environment. DISCLAIMER: This comparison reflects the latest versions offered by each vendor as of November 2025. Details are compiled from publicly available websites, forums, and customer reviews. Choose IPNetwork Monitor for simpler, more complete network monitoring 1 65+ prebuilt Application Templates 2 10+ notification/alert delivery methods 3 40+ monitor types 4 Per-monitor licensing that stays simple — plus a free 50-monitor tier IPNetwork Monitor helps you achieve practical infrastructure monitoring without relying on a maze of add-ons. It covers core protocols and integrations—SNMP/WMI for Windows and network gear, SSH for Linux/Unix, HTTP(S) for web endpoints, ODBC for database checks, and script-based monitors for everything else. Where many tools lean heavily toward APM-first use cases, IPNetwork Monitor emphasizes end-to-end infrastructure visibility and the operational workflows network teams depend on. Trusted by teams—see why they choose IPNetwork Monitor Accelerated time to value Roll out quickly and begin generating meaningful alerts and insights with minimal ramp-up. Local-first security Credentials and configuration data are stored locally on your machine, maintaining full ownership and control. All-in-one monitoring Monitor servers, SNMP-enabled devices, services, and HTTP(S) checks in a unified interface. Frequently Asked Questions about IPNetwork Monitor vs Datadog Check out our Knowledge Base where we answer questions regarding various topics When should I choose IPNetwork Monitor instead of Datadog? Choose IPNetwork Monitor if you want an on-premises solution you fully control (data, credentials, retention) with a unified desktop + web experience and straightforward per-monitor licensing. Datadog is often a fit for cloud-first teams that can invest in multiple modules and agent-based instrumentation, but costs and operational complexity can grow as you add hosts, logs, and features. To see what IPNetwork Monitor looks like in practice, visit IPNetwork Monitor Demo . How does setup complexity differ between the two products? IPNetwork Monitor typically starts with discovery wizards and templates, so you can get meaningful uptime and performance monitoring quickly without deploying lots of agents. Datadog usually requires installing and maintaining agents across many hosts and enabling separate components for full visibility. For a quick, guided start with IPNetwork Monitor, follow Quick Start: Monitor a Small Network and Network Discovery . Can IPNetwork Monitor provide full-stack visibility without buying extra modules? Yes—IPNetwork Monitor covers core infrastructure and service monitoring (SNMP/WMI/SSH/HTTP(S)/ODBC, syslog, scripts), plus built-in reporting, trends, and web transaction monitoring for end-user experience checks. You can apply application templates for common systems and still customize monitors as needed. Start with Monitor Types and Application Monitoring Templates . How can I reduce alert noise and build reliable alerting in IPNetwork Monitor? Use monitor dependencies and state conditions to prevent cascades when an upstream device fails, and add spike filters and thresholds to avoid alerts from brief blips. Then attach multiple “simple actions” (email, scripts, HTTP requests, etc.) with schedules to support escalations and recoveries. See Monitor Dependencies and State Conditions . What are the security and sensitive-data advantages of IPNetwork Monitor compared to a SaaS platform? IPNetwork Monitor keeps configuration, credentials, and monitoring history on-premises under your control, and supports secure protocols like SNMPv3, SSH, and HTTPS (plus syslog and Windows Event Log for security-relevant events). With SaaS monitoring, telemetry and configuration live outside your environment and depend on internet connectivity and vendor-hosted storage. For hardening guidance, review Security Considerations and configure an Access Password . IPNetwork Monitor is 100% SELF-HOSTED Complete data ownership & control Configs, metrics, and alert history never leave your network. Deploy behind your firewall Run on-prem or in your VPC with your own access policies. Keep passwords on your hardware Credentials and secrets are stored locally, not in someone else’s cloud. No recurring subscription fees Predictable, one-time licensing. No surprise overages. Full network privacy & security Zero 3rd-party data processing. Keep traffic and logs private. No external data transmission Operate even in isolated or regulated environments. IPNetwork Monitor vs. other monitoring tools vs. LogicMonitor vs. PRTG vs. SolarWinds vs. Datadog --- - [IPNetwork Monitor vs LogicMonitor | IPNetwork Monitor](https://ipnetwork-monitor.com/comparison/ipnm-vs-logicmonitor/): Criteria IPNetwork Monitor LogicMonitor Platform On-premises Windows-based monitoring with unified desktop & web UI. Cloud-hosted platform oriented toward hybrid IT monitoring in larger environments. Agents Remote Network Agent for distributed networks. Primarily agentless collectors designed to simplify rollout in bigger, distributed estates. Pricing Simple per-monitor licensing with a free 50-monitor tier. Subscription pricing is geared ### IPNetwork Monitor vs LogicMonitor #### Why choose us as your Network Monitor solution? #### See why teams choose IPNetwork Monitor ##### Fast time to value ##### Sensitive Data Protection ##### Unified network monitoring #### Frequently Asked Questions about IPNetwork Monitor vs LogicMonitor ##### IPNetwork Monitor is 100% SELF-HOSTED #### IPNetwork Monitor vs. other monitoring tools #### Try IPNetwork Monitor for Free ✕ IPNetwork Monitor vs LogicMonitor See how IPNetwork Monitor compares on setup, pricing, scalability, alerting, dashboards, and more. Try IPNetwork Monitor Criteria IPNetwork Monitor LogicMonitor Platform On-premises Windows-based monitoring with unified desktop & web UI. Cloud-hosted platform oriented toward hybrid IT monitoring in larger environments. Agents Remote Network Agent for distributed networks. Primarily agentless collectors designed to simplify rollout in bigger, distributed estates. Pricing Simple per-monitor licensing with a free 50-monitor tier. Subscription pricing is geared toward larger deployments, with an emphasis on predictable enterprise spend. Scalability Scales from small sites to distributed networks via agents. Built to scale to very large estates, and most attractive for organizations already operating at enterprise scale. Integrations Open protocols (SNMP, WMI, syslog, SSH, HTTP/S, ODBC) and custom scripts instead of heavy proprietary plug-ins. Catalog of thousands of pre-built integrations, with a strong focus on mainstream enterprise technologies. Alerts Flexible alert rules with multiple delivery and script actions. Applies machine learning to correlate and automatically close alerts, reducing manual triage in complex setups. Visibility Full-stack view from basic uptime to traffic, databases, system resources and synthetic web transactions. Aims to deliver broad, “full-stack” visibility for hybrid IT when most layers of the stack are instrumented. Dashboards Clear status views in desktop and web consoles. Includes numerous ready-made dashboards that shine once the monitored environment has been fully modeled. Logs / Search Central event log and monitor logs with time-range filters, state change history and sortable web reports. Provides log search and correlation so syslog messages can be tied directly to alerts and monitored objects. Adoption / Training Quick Start guides, discovery wizards and application templates make initial setup fast even for small teams. Modern web interface that can be adapted to team workflows, though tuning usually takes some initial effort. Monitoring 40+ monitor types covering network devices, Windows/Linux servers, databases, web apps, traffic, syslog and more. Collector-based monitoring designed to remain efficient on monitored systems, particularly in larger rollouts. Deployment Installs on Windows with optional remote agents and a built-in web UI – no external database or SaaS tenancy required. Cloud delivery and collectors can speed initial rollout when standardized deployment processes are in place. Retention Flexible history retention for reports and analysis. Offers long-term data retention as part of the service, aligned with enterprise reporting requirements. Analytics Built-in graphs, trend analysis and issue reports provide practical performance analytics without extra modules. Includes NetFlow and traffic analysis capabilities aimed at high-volume network environments. Distribution Remote Network Agents enable secure monitoring of remote subnets, including those without Windows hosts. Supports distributed tracing via OpenTelemetry for organizations instrumenting microservices and cloud-native apps. Experience Single monitoring server with integrated Windows and web interfaces, reports and admin tools in one place. Positions itself as a single pane of glass over hybrid resources via a consolidated enterprise console. Value Rich monitoring, alerting and reporting at SMB-friendly pricing plus a perpetual free tier for smaller environments. Uses pre-trained AI/ML models intended to surface insights quickly once enough environment data is collected. Support Email support with comprehensive documentation. Provides 24/7 support and professional services oriented toward larger customers, plus an active user community. Noise reduction Monitor dependencies and state conditions reduce alert storms. Edwin AI is promoted as significantly cutting alert noise and correlating related events in busy environments. Security Supports protocols like SNMP v3, SSH and HTTPS plus syslog and Windows Event Log monitoring for security-relevant events. Implements enterprise security practices, including support for the SNMP v3 security model. API Support HTTP/SSH integrations; MCP API coming next release. Offers a comprehensive REST API designed for integration with existing enterprise tools and workflows. Sensitive Data Protection On-premises solution storing all credentials and configuration data locally in a secure RDBMS under full user control. Runs as a SaaS platform, so configuration data and telemetry are processed and stored in LogicMonitor’s cloud. DISCLAIMER: This comparison reflects the latest versions offered by each vendor as of November 2025. Details are compiled from publicly available websites, forums, and customer reviews. Why choose us as your Network Monitor solution? 1 More then 65 out of box Application Templates 2 Over 10 Notification methods 3 More than 40 Monitor Types 4 Simple per-monitor licensing with a free 50-monitor tier IPNetwork Monitor is a practical choice when you want broad, “real-world” monitoring without building a complex stack of add-ons. It covers the common network and server protocols (SNMP/WMI/SSH/HTTP(S)/ODBC, plus scripts) and lets you stand up monitoring quickly using Network Discovery, the New Monitor Wizard, and application templates—so even a small team can get to useful alerts and reports fast while still keeping the setup fully customizable as you grow. Unlike tools focused mainly on APM, we prioritize full infrastructure visibility and practical network monitoring workflows. See why teams choose IPNetwork Monitor Fast time to value Deploy quickly and start getting actionable alerts without long onboarding. Sensitive Data Protection All credentials and configuration data stored on your local machine under full user control. Unified network monitoring Monitor servers, SNMP devices, services, and web checks in one place. Frequently Asked Questions about IPNetwork Monitor vs LogicMonitor Check out our Knowledge Base where we answer questions regarding various topics Which tool is a better fit for a small or mid-sized IT team? If you want an on-premises monitoring server you fully control (data, credentials, retention) with straightforward per-monitor licensing, IPNetwork Monitor is typically a better match for small-to-mid environments and lean teams. If you already operate at enterprise scale and want a cloud-hosted platform with extensive pre-built integrations and enterprise-focused workflows, LogicMonitor may be the better fit. To see IPNetwork Monitor in action first, start with IPNetwork Monitor Demo . How do deployment and data ownership differ between IPNetwork Monitor and LogicMonitor? IPNetwork Monitor is installed on your Windows server and stores configuration and monitoring data locally under your control, which is often important for compliance and sensitive environments. LogicMonitor is SaaS-based, so telemetry and configuration are processed and stored in the vendor cloud, with collectors bridging to your infrastructure. If you want practical guidance for on-prem hardening, review Security Considerations . Can IPNetwork Monitor cover the same monitoring breadth without a huge integration catalog? Yes—IPNetwork Monitor focuses on open protocols and flexible monitors (SNMP/WMI/SSH/HTTP(S)/ODBC, scripts, syslog) so you can monitor a wide range of devices and services without relying on proprietary plug-ins. For common use cases, application templates speed up rollout while still letting you customize what is collected and how it is alerted on. See Monitor Types and Application Monitoring Templates . How do I reduce alert noise in IPNetwork Monitor (comparable to correlation approaches)? Start by modeling dependencies and using state conditions so downstream alerts don’t cascade when a parent device is down, then add spike filters and sensible thresholds so brief glitches don’t trigger notifications. This keeps alerts actionable even as you scale the number of monitors and polling frequency. For details, see Monitor Dependencies and State Conditions . How can I monitor remote sites or segmented networks with IPNetwork Monitor? Use Remote Network Agents to securely monitor remote subnets (including locations without a local Windows host) while keeping the main server centralized and on-prem. This approach helps distribute monitoring load and keeps connectivity simple across firewalls and WAN links. Start with Remote Network Agents , and for Linux deployments see Remote Network Agents (Linux) . IPNetwork Monitor is 100% SELF-HOSTED Complete data ownership & control Configs, metrics, and alert history never leave your network. Deploy behind your firewall Run on-prem or in your VPC with your own access policies. Keep passwords on your hardware Credentials and secrets are stored locally, not in someone else’s cloud. No recurring subscription fees Predictable, one-time licensing. No surprise overages. Full network privacy & security Zero 3rd-party data processing. Keep traffic and logs private. No external data transmission Operate even in isolated or regulated environments. IPNetwork Monitor vs. other monitoring tools vs. LogicMonitor vs. PRTG vs. SolarWinds vs. Datadog --- - [IPNetwork Monitor vs PRTG | IPNetwork Monitor](https://ipnetwork-monitor.com/comparison/ipnm-vs-prtg/): Criteria IPNetwork Monitor PRTG Platform On-premises Windows-based monitoring with unified desktop & web UI. Windows-based monitoring built around local probes and on-premises deployment, without a single unified desktop-plus-web experience. Agents Remote Network Agent for distributed networks. Uses remote probes to reach distributed sites, which still require manual rollout, configuration and maintenance. Pricing Simple per-monitor licensing ### IPNetwork Monitor vs PRTG #### Why teams choose IPNetwork Monitor for network monitoring #### See what makes IPNetwork Monitor the go-to choice ##### Faster time to value ##### Sensitive data stays protected ##### All-in-one network monitoring #### Frequently Asked Questions about IPNetwork Monitor vs PRTG ##### IPNetwork Monitor is 100% SELF-HOSTED #### IPNetwork Monitor vs. other monitoring tools #### Try IPNetwork Monitor for Free ✕ IPNetwork Monitor vs PRTG See how IPNetwork Monitor compares on setup, pricing, scalability, alerting, dashboards, and more. Try IPNetwork Monitor Criteria IPNetwork Monitor PRTG Platform On-premises Windows-based monitoring with unified desktop & web UI. Windows-based monitoring built around local probes and on-premises deployment, without a single unified desktop-plus-web experience. Agents Remote Network Agent for distributed networks. Uses remote probes to reach distributed sites, which still require manual rollout, configuration and maintenance. Pricing Simple per-monitor licensing with a free 50-monitor tier. Unexpected pricing and licensing changes can make long-term budgeting difficult. Scalability Scales from small sites to distributed networks via agents. Best suited to smaller environments, with scalability becoming limited once you move beyond roughly 500 monitored devices. Integrations Open protocols (SNMP, WMI, syslog, SSH, HTTP/S, ODBC) and custom scripts instead of heavy proprietary plug-ins. Advertises 250+ “technology partners,” but device coverage, ITSM options (primarily ServiceNow) and public cloud integrations remain comparatively narrow. Alerts Flexible alert rules with multiple delivery and script actions. Alerts typically have to be acknowledged and closed manually, increasing day-to-day operational workload. Visibility Full-stack view from basic uptime to traffic, databases, system resources and synthetic web transactions. Emphasises infrastructure status, with less built-in focus on end-to-end application and transaction visibility. Dashboards Clear status views in desktop and web consoles. Does not provide rich pre-built dashboards; visual “Maps” typically need to be constructed manually via drag-and-drop. Logs / Search Central event log and monitor logs with time-range filters, state change history and sortable web reports. Only basic syslog handling is available, with limited ability to ingest, correlate and search logs at scale. Adoption / Training Quick Start guides, discovery wizards and application templates make initial setup fast even for small teams. Initial configuration can be time-consuming, and more advanced usage often relies on trial-and-error or external guidance. Monitoring 40+ monitor types covering network devices, Windows/Linux servers, databases, web apps, traffic, syslog and more. Lacks native Kubernetes (k8s) monitoring, reducing coverage for containerised workloads. Deployment Installs on Windows with optional remote agents and a built-in web UI – no external database or SaaS tenancy required. Windows-based core with additional remote probes for other networks, which adds design and maintenance overhead in complex environments. Retention Flexible history retention for reports and analysis. Historical retention is constrained by the underlying Windows server and database sizing, requiring careful capacity planning for longer-term data. Analytics Built-in graphs, trend analysis and issue reports provide practical performance analytics without extra modules. Provides only basic trends; deeper analytics often require external reporting tools or manual data export. Distribution Remote Network Agents enable secure monitoring of remote subnets, including those without Windows hosts. Remote probes extend monitoring to branch offices, but each probe is another Windows system that must be deployed, secured and updated. Experience Single monitoring server with integrated Windows and web interfaces, reports and admin tools in one place. The combination of sensors, probes and maps can feel fragmented compared with a single, fully integrated monitoring console. Value Rich monitoring, alerting and reporting at SMB-friendly pricing plus a perpetual free tier for smaller environments. Per-sensor licensing can look attractive initially but becomes harder to predict and more expensive as monitored metrics and devices grow. Support Email support with comprehensive documentation. Professional services are very limited, and there is no live chat or phone-based support for faster resolution. Noise reduction Monitor dependencies and state conditions reduce alert storms. Users often encounter overwhelming alert noise, with no AI-assisted correlation to automatically group or suppress related events. Security Supports protocols like SNMP v3, SSH and HTTPS plus syslog and Windows Event Log monitoring for security-relevant events. Tends to rely on older SNMP v1/v2 polling; SNMPv3 is supported but reported to significantly impact performance and scalability when enabled. API Support HTTP/SSH integrations; MCP API coming next release. API coverage is incomplete, limiting automation and enterprise integration; some object types cannot be created and many settings cannot be configured programmatically. Sensitive Data Protection On-premises solution storing all credentials and configuration data locally in a secure RDBMS under full user control. Also on-premises, but credential protection and encryption options are more limited than modern best practices. DISCLAIMER: This comparison reflects the latest versions offered by each vendor as of November 2025. Details are compiled from publicly available websites, forums, and customer reviews. Why teams choose IPNetwork Monitor for network monitoring 1 65+ ready-to-use Application Templates 2 10+ notification methods 3 40+ monitor types 4 Simple per-monitor licensing — including a free 50-monitor tier IPNetwork Monitor is a one-stop solution for monitoring servers, network devices, and critical services with instant alerts and clear reporting. While some platforms focus mainly on APM, we focus on infrastructure visibility and practical network monitoring workflows—so you can move quickly today and still customize as you scale. See what makes IPNetwork Monitor the go-to choice Faster time to value Get up and running quickly and start receiving actionable alerts—without a long onboarding process. Sensitive data stays protected Credentials and configuration stay on your local machine, fully under your control. All-in-one network monitoring Monitor servers, SNMP devices, services, and web checks in one place. Frequently Asked Questions about IPNetwork Monitor vs PRTG Check out our Knowledge Base where we answer questions regarding various topics Which tool is better for a small-to-mid network: IPNetwork Monitor or PRTG? If you want a single, unified monitoring experience (desktop + web) with quick setup wizards and templates, IPNetwork Monitor is usually easier to deploy and operate for small-to-mid environments. PRTG can work well for simpler setups, but day-to-day management can become more time-consuming as sensors/probes grow. To get started fast, see Quick Start: Monitor a Small Network . How do IPNetwork Monitor Remote Network Agents compare to PRTG remote probes for distributed sites? IPNetwork Monitor uses Remote Network Agents to securely monitor remote subnets (including sites without Windows hosts), while keeping everything managed from one place. PRTG remote probes can extend monitoring too, but each probe is another Windows system you must deploy, secure, update, and maintain. For IPNetwork Monitor, see Remote Network Agents . How can I reduce alert noise and avoid alert storms in IPNetwork Monitor? Use monitor dependencies and state conditions so downstream services don’t flood you with alerts when an upstream device is down, and add spike filters and sensible thresholds to prevent brief blips from triggering notifications. This is especially important as you scale polling frequency and monitor count. Start here: Monitor Dependencies and State Conditions . Does IPNetwork Monitor provide better reporting and history than PRTG? IPNetwork Monitor includes built-in graphs, trend analysis, sortable reports, and flexible history retention for troubleshooting and capacity planning—without needing external reporting tools for many common tasks. If you want to tune retention and keep the monitoring database healthy over time, review DB Maintenance and Reports . How does IPNetwork Monitor handle security and sensitive data compared to PRTG? IPNetwork Monitor is on-premises and keeps configuration data and credentials locally under your control, using encryption for stored sensitive values and supporting secure protocols like SNMPv3, SSH, and HTTPS. To harden a new deployment and avoid common security mistakes, follow Security Considerations and set an access password as described in Access Password . IPNetwork Monitor is 100% SELF-HOSTED Complete data ownership & control Configs, metrics, and alert history never leave your network. Deploy behind your firewall Run on-prem or in your VPC with your own access policies. Keep passwords on your hardware Credentials and secrets are stored locally, not in someone else’s cloud. No recurring subscription fees Predictable, one-time licensing. No surprise overages. Full network privacy & security Zero 3rd-party data processing. Keep traffic and logs private. No external data transmission Operate even in isolated or regulated environments. IPNetwork Monitor vs. other monitoring tools vs. LogicMonitor vs. PRTG vs. SolarWinds vs. Datadog --- - [IPNetwork Monitor vs SolarWinds | IPNetwork Monitor](https://ipnetwork-monitor.com/comparison/ipnm-vs-solarwinds/): Criteria IPNetwork Monitor SolarWinds Platform On-premises Windows-based monitoring with unified desktop & web UI. Primarily Windows-server-based platform with a web console and add-on modules for specific functions. Agents Remote Network Agent for distributed networks. Combines agents and polling engines, which can increase deployment and maintenance overhead in large environments. Pricing Simple per-monitor licensing with a ### IPNetwork Monitor vs SolarWinds #### Why IPNetwork Monitor is the practical choice for network monitoring #### Discover why teams choose IPNetwork Monitor ##### Quick setup, faster results ##### Keep sensitive data under your control ##### One platform for infrastructure monitoring #### Frequently Asked Questions about IPNetwork Monitor vs SolarWinds ##### IPNetwork Monitor is 100% SELF-HOSTED #### IPNetwork Monitor vs. other monitoring tools #### Try IPNetwork Monitor for Free ✕ IPNetwork Monitor vs SolarWinds See how IPNetwork Monitor compares on setup, pricing, scalability, alerting, dashboards, and more. Try IPNetwork Monitor Criteria IPNetwork Monitor SolarWinds Platform On-premises Windows-based monitoring with unified desktop & web UI. Primarily Windows-server-based platform with a web console and add-on modules for specific functions. Agents Remote Network Agent for distributed networks. Combines agents and polling engines, which can increase deployment and maintenance overhead in large environments. Pricing Simple per-monitor licensing with a free 50-monitor tier. Module- and element-based licensing that can make total costs less predictable as your environment expands. Scalability Scales from small sites to distributed networks via agents. Faces scaling issues with log collection and event downloads, and tends to hit limits around 20,000 devices/nodes. Integrations Open protocols (SNMP, WMI, syslog, SSH, HTTP/S, ODBC) and custom scripts instead of heavy proprietary plug-ins. Smaller integration catalog that can leave monitoring blind spots for some technologies. Alerts Flexible alert rules with multiple delivery and script actions. Robust alerting features, but significant manual tuning is often required to keep alert noise under control. Visibility Full-stack view from basic uptime to traffic, databases, system resources and synthetic web transactions. Does not offer native multi-account visibility; each account typically has to be configured separately. Dashboards Clear status views in desktop and web consoles. Custom dashboards are available, but usually need to be built and tailored manually for each team or use case. Logs / Search Central event log and monitor logs with time-range filters, state change history and sortable web reports. Deeper log search and correlation typically rely on separate log-analysis tools or add-on components. Adoption / Training Quick Start guides, discovery wizards and application templates make initial setup fast even for small teams. Generally requires formal training and dedicated resources to operate and maintain effectively. Monitoring 40+ monitor types covering network devices, Windows/Linux servers, databases, web apps, traffic, syslog and more. Supports a wide range of devices, but many advanced checks depend on purchasing and managing additional modules. Deployment Installs on Windows with optional remote agents and a built-in web UI – no external database or SaaS tenancy required. Initial deployment and configuration can be complex, resource-intensive, and time-consuming. Retention Flexible history retention for reports and analysis. Long-term data retention is constrained by database sizing and may require extra storage and administration effort. Analytics Built-in graphs, trend analysis and issue reports provide practical performance analytics without extra modules. Provides performance charts, but more advanced analytics often depend on external reporting or BI tooling. Distribution Remote Network Agents enable secure monitoring of remote subnets, including those without Windows hosts. Remote polling engines support distributed sites, but each additional engine adds infrastructure and configuration overhead. Experience Single monitoring server with integrated Windows and web interfaces, reports and admin tools in one place. Presents multiple components that feel more like a collection of tools than a single, unified experience. Value Rich monitoring, alerting and reporting at SMB-friendly pricing plus a perpetual free tier for smaller environments. AI/ML-driven insights can generate a high volume of false positives during the first 6–9 months of tuning. Support Email support with comprehensive documentation. Support responses can be slow, particularly during peak periods. Noise reduction Monitor dependencies and state conditions reduce alert storms. Alert thresholds and suppression rules must largely be tuned by hand to avoid alert storms. Security Supports protocols like SNMP v3, SSH and HTTPS plus syslog and Windows Event Log monitoring for security-relevant events. Security relies heavily on hardening on-premises servers and databases, increasing the customer’s operational responsibility. API Support HTTP/SSH integrations; MCP API coming next release. Exposes APIs and SDKs, but meaningful automation generally requires custom scripting and knowledge of the underlying data model. Sensitive Data Protection On-premises solution storing all credentials and configuration data locally in a secure RDBMS under full user control. Hybrid and on-premises products have experienced notable security incidents in the past. DISCLAIMER: This comparison reflects the latest versions offered by each vendor as of November 2025. Details are compiled from publicly available websites, forums, and customer reviews. Why IPNetwork Monitor is the practical choice for network monitoring 1 65+ out-of-the-box Application Templates 2 10+ ways to send alerts and notifications 3 40+ monitor types for networks, servers, and services 4 Straightforward per-monitor licensing with a free 50-monitor tier IPNetwork Monitor is a strong fit if you want wide coverage and fast deployment without turning monitoring into a separate engineering project. It supports the protocols teams rely on every day—SNMP, WMI, SSH, HTTP(S), ODBC, and scripting—so you can monitor both standard infrastructure and custom services. Instead of being centered only on APM, IPNetwork Monitor is designed to deliver full infrastructure visibility and the workflows that network teams actually use. Discover why teams choose IPNetwork Monitor Quick setup, faster results Deploy in minutes and start turning issues into actionable alerts—no lengthy onboarding required. Keep sensitive data under your control Store credentials and configuration locally, so you remain in charge of access and security. One platform for infrastructure monitoring Track servers, SNMP devices, services, and web endpoints from a single dashboard. Frequently Asked Questions about IPNetwork Monitor vs SolarWinds Check out our Knowledge Base where we answer questions regarding various topics When does IPNetwork Monitor make more sense than SolarWinds? Choose IPNetwork Monitor if you want a single on-premises Windows install with an integrated desktop + web experience, fast onboarding (wizards/templates), and predictable per-monitor licensing. SolarWinds is often chosen for large, module-driven environments, but it can require more components, training, and ongoing tuning to keep operations efficient. If you want a quick product tour before installing, see IPNetwork Monitor Demo . How is deployment and day-to-day maintenance different compared to SolarWinds modules? IPNetwork Monitor installs as one monitoring server with built-in admin tools, reports, and a web UI, and it scales to distributed sites using Remote Network Agents when needed. SolarWinds commonly grows into multiple servers/components (polling engines, add-on modules), which can increase deployment time and ongoing maintenance overhead. For distributed networks with IPNetwork Monitor, start with Remote Network Agents . How do I keep alerts actionable and avoid alert storms in IPNetwork Monitor? Build alerting around dependencies and state conditions so downstream monitors don’t cascade when an upstream device fails, then add spike filters and sensible thresholds to reduce noise from brief glitches. You can also attach multiple simple actions (email, scripts, HTTP requests, etc.) with schedules for escalations and recoveries. See Monitor Dependencies and State Conditions . Does IPNetwork Monitor provide reporting and analytics without extra modules? Yes—IPNetwork Monitor includes built-in graphs, trends, issue reports, and web reports so you can troubleshoot and plan capacity without buying separate analytics modules. You can also control how long history is retained to balance troubleshooting needs with storage usage. Review Reports and DB Maintenance . What are the security advantages of IPNetwork Monitor if I’m worried about sensitive data? IPNetwork Monitor keeps credentials and monitoring configuration on-premises under your control, supports secure protocols like SNMPv3, SSH, and HTTPS, and can monitor security-relevant events via syslog and Windows Event Log. For a hardened setup, avoid default access settings and follow recommended practices on Security Considerations , including configuring an Access Password . IPNetwork Monitor is 100% SELF-HOSTED Complete data ownership & control Configs, metrics, and alert history never leave your network. Deploy behind your firewall Run on-prem or in your VPC with your own access policies. Keep passwords on your hardware Credentials and secrets are stored locally, not in someone else’s cloud. No recurring subscription fees Predictable, one-time licensing. No surprise overages. Full network privacy & security Zero 3rd-party data processing. Keep traffic and logs private. No external data transmission Operate even in isolated or regulated environments. IPNetwork Monitor vs. other monitoring tools vs. LogicMonitor vs. PRTG vs. SolarWinds vs. Datadog --- ## Help - [Adding Monitors Manually | IPNetwork Monitor](https://ipnetwork-monitor.com/help/adding-monitors-manually/): You can add separate monitor(s) and apply template(s) to a host manually using the New Monitor Wizard instead of running network discovery. The wizard is available from the program toolbar, as well as from the menu. Once the wizard starts, you are offered to choose a list of monitors to create and templates to apply. ### Adding Monitors Manually #### Try IPNetwork Monitor for Free ✕ You can add separate monitor(s) and apply template(s) to a host manually using the New Monitor Wizard instead of running network discovery. The wizard is available from the program toolbar, as well as from the menu. Once the wizard starts, you are offered to choose a list of monitors to create and templates to apply. The monitors and templates are grouped by categories. The categories are listed on the left pane.To create separate monitors select a monitor category on the left pane and select the appropriate monitor type(s) on the right pane. To apply a template to the host select a template category on the left pane and select a template(s) on the right pane. A template allows to create several preconfigured monitors on the selected host at once. In the sample below the Linux Server application template is selected: it contains various monitors that check overall Linux system health. Also, you can filter monitors and templates by name or keyword, for example, ‘HTTP’ keyword allows to find 2 monitors that use HTTP protocol, and 8 templates that use HTTP(S) monitors: Another option to simplify search for specific monitors or templates is to use filters. Click Filter by… button and select any combination (and/or) of protocols and resource types to find if there exists a monitor or template that uses the selected protocol(s) and/or monitors the selected resources: The filtering result contains both monitors and templates that use the specified protocol (WMI) and monitor the specified resources (CPU and memory usage, disk space usage and processes): To view and modify the selected monitors and templates list click “Selected monitors” link at the bottom right corner of this page: You can unselect any of previously selected monitors or templates and they will not be created. Three monitors will be created in this example: PING, HTTP(S) and SNMP CPU usage, and Linux Server application template will be applied to the selected host: Click Next button after the monitors and templates list is finalized. On the second page you need to select a host for these new monitors and templates. Specify either a host domain name or IP address. You can select an existing host (the one you have already added or discovered): When you select a host that has applications created, you are provided an option to add new monitors to any existing application: Alternatively, you can create a new host here: enter a new host name or address. A hint below the host name text field indicates that you are about to create a new host. You will specify remaining host settings on the next page. To start the newly created monitors (both single monitors and monitors in a template) immediately after they are created, select the ‘Start the monitor(s)’ checkbox near the page bottom: If you selected a single monitor of the following types: HTTP(S), WTM or FTP, the second page allows you to select a URL to monitor instead of DNS hostname or IP address: Here you can specify exact URL to monitor: You can create a new host or attach new monitor to any existing host on this page. The third page appears only if you create a new host. It allows you to define key parameters for this host. Here you can change: a human-readable host display name; a Remote Agent for the new host and a host group (use the ‘Change Host Group…’ button to alter these settings); a custom icon; a way to access the host: either by its domain name, or using the IP address; credentials to be used by the host monitors. Credentials are inherited from the host group by default. You can break the inheritance and specify custom values here. You will also be able to define custom credentials for each individual monitor later. The last page allows you to edit settings for the newly created monitors. The page contains three tabs that match the Parameters/Results Pane tabs. You can skip this step and change any monitor or template parameter from Parameters/Results Pane at any time after the New Monitor wizard is closed. However, some monitors require initial manual configuration and may start in Down state if not configured. Select the monitor on the page left side and review and/or modify its parameters. On the first tab (Main parameters tab) you can define or modify monitor-specific parameters such as a HTTP URL to check as well as generic parameters (polling interval, regular reporting configuration, and so on). Optional HTTP proxy server with authentication is specified in this example: On the second tab (State conditions tab) you can change the default monitor state conditions, i.e. the conditions that define when the monitor changes its state. Optional HTTP response validation is enabled in this example: the monitor should switch to Down state if the sever response does not contain “Hello from” string: On the third tab (Alerting tab) you can change the default monitor alerts, i.e. the rules that define how the monitoring system should inform you of monitor state changes or events generated by the monitor. This sample uses the default alerts that are inherited from the monitor parent host: An SNMP CPU monitor is selected in the sample below, and its state conditions are modified: the monitor will change its state to Warning if a poll shows the CPU load greater than 90%: If you select a template on the left pane of this page, you will be able to configure it: change its name, if necessary, enable/disable the monitors, and modify other group node parameters: Polling interval, Dependency settings, Regular reporting and Credentials. Disabled monitors are shown in gray color on the left pane and unchecked on the Main tab. In the sample below several template monitors have been enabled in addition to the default ones: The monitors marked orange on the left pane require manual configuration (network interface number, database name or other parameter that can’t be obtained from the host automatically, should be specified). Select the monitor on the left pane and set the required parameters. You can skip this step and apply the template without configuring such monitors, and set their parameters later. However, in this case such monitor may be created in Down state. In the sample below two traffic monitors are marked orange on the left pane, and the template itself is marked orange, too. The yellow banner above the selected traffic speed monitor Main tab lists the parameter(s) that requires configuration: Interface Number. After the parameter is configured the banner changes its color to green. The monitor is ready to start. The template itself is no longer marked orange: all its monitors are configured. Click Finish button to create new monitors and template. The new monitors and templates and the new host (if one is created here) will appear in your monitoring system immediately after you click Finish . The single monitors and templates are multiselected in Tree View, so that you can poll them, or stop them all, or mark as Favorites. --- - [Alerting and Actions | IPNetwork Monitor](https://ipnetwork-monitor.com/help/alerting-and-actions/): IPNetwork Monitor provides various methods of automatic response to monitored resource state changes. Prompt and informative notification on a monitored resource operation failure allows you to substantially reduce the downtime of important resources, which saves the users work time and improves administrator work effectiveness. The following notification methods can be used: e-mail notification, SMS over ### Alerting and Actions #### Try IPNetwork Monitor for Free ✕ IPNetwork Monitor provides various methods of automatic response to monitored resource state changes. Prompt and informative notification on a monitored resource operation failure allows you to substantially reduce the downtime of important resources, which saves the users work time and improves administrator work effectiveness. The following notification methods can be used: e-mail notification, SMS over GSM modem or e-mail, instant messaging (using any XMPP client), sending a message to another computer, sending Push notification to a mobile device, playing a sound file, and displaying a message in a dialog or pop-up window. Also, the monitoring service can do the following, if a monitor changes its state, or if an event occurs: run a program or script on local machine, run a program or script on local or remote machine via SSH, set SNMP value on local or remote SNMP-enabled machine. send HTTP(S) request The default notification message body contains a short problem description and a problem timeframe (if available). Also, it is possible to specify a program to run as an alerting action. You can use these actions to implement complex methods to respond to a problem state: for example, to start/stop a given service on a remote machine, or to reboot a given remote machine. In order to get a notification on a resource state change an alerting rule should be assigned to the resource monitor on the monitor’s Alerting tab . The alerting rule assigned to the resource monitor (or any other entity) consists of commands (or command sequences) that the monitoring system executes on a monitor state change. Each command (or command sequence) is named an alert . Each alert is a set of simple actions and a time schedules assigned to them. The monitoring system executes a simple action (as a command in the monitor alerting rule) only in the assigned to this simple action schedule timeframe. There are three predefined alerts and one alerting rule, hence you are not required to create alerts or rules to start getting notifications, you can use the predefined ones. Let’s consider an example . A monitor is set to check a CPU usage on a certain host and configured to switch to Down state if the CPU load is too high. We need to notify a system administrator with an e-mail message and a pop-up window if the monitor switches to Down state and remains in this state for 10 seconds. Also we need to notify the senior system administrator via e-mail if the problem still persists within 30 minutes after it was encountered (i.e., if the CPU load is still high), but escalate on worktime only. Also, we need to notify the administrator if the monitor switches to OK state, i.e. if the problem is resolved. For this particular case we need to create four alerts on Settings -> Alerts tab: Down (e-mail + pop-up) alert that will be executed in 10 seconds after the problem occurs, both simple actions: e-mail and pop-up will be executed 24/7: Escalation (e-mail to Senior Administrator) alert that will be sent in 30min if the problem still persists, this e-mail simple action will be executed on worktime only: Recovery from down (e-mail) alert that will be sent after the problem is resolved, this e-mail simple action will be executed 24/7: Recovery from escalated down (e-mail to Senior Administrator) alert that will be sent after the long-term problem is resolved, i.e. if the resource switches to OK state after the long (in this case 30min) Down. This simple action will be executed on worktime only: Note: there is no need to create four different alerts in this case. You can create one alert (e.g., e-mail + pop-up) and use it for all four state changes. I.e., you can create four different alerts for all four state changes: a problem occurs monitor recovers from the problem state monitor remains in the problem state for a long time (escalation) monitor recovers from the escalated problem state but you can use one alert for all these state transitions as well. The detailed description of how to create and modify an alert is here . After the alerts are created we need to construct an alerting rule on the Settings -> Alerting Rules tab: let’s assign our alerts to the monitor state changes. In the Down State Alerts section we select Down (e-mail to Administrator + pop-up) alert from drop-down list to be executed when the monitor enters Down state. We check escalation checkbox (‘When monitor remains in Down state…’), set the escalation time limit (30 min) and frequency (repeat every 30 min), and select Escalation (e-mail) alert . We check recovery checkbox and select Recovery from down (e-mail) alert to be executed upon recovery from Down state. There is no need to configure Warning State Alerts and Event Alert sections, since we don’t need to inform anyone about these state changes in this example. This is our final example alerting rule as it is constructed on the Settings -> Alerting Rules tab: Now we can assign this alerting rule to our CPU usage monitor on the monitor Alerting tab . The detailed description of how to create and modify an alerting rule is here . Note: all the alerts are reusable and can be used to construct more alerting rules. Note: all the named alerting rules are reusable, too. The rule constructed in this example can be assigned to any tree node, e.g. to other monitors, not only to the monitor we use in this example. Alerting Rules An alerting rule specifies what the monitoring service should do when a monitor changes its state or an event takes place. I.e., each alerting rule is a reusable template that tells the monitoring service how to respond to monitor state changes and events. The rules assigned to a host or named rules simplify monitoring system configuration. A named alerting rule can be assigned to any node in the host tree: a root, agent, host group, host or monitor on the node Alerting tab . On the Settings -> Alerting Rules tab you can manage named alerting rules: create new alerting rules, edit and delete existing ones. The bottom part of the page contains a short description of the selected rule. The image below shows Settings -> Alerting Rules tab with selected alerting rule: Each alerting rule consists of three sections; any of them can be empty. The sections are: Alert(s) to execute on OK -> Down and Down -> OK transitions (Down State Alerts): Alert(s) to execute on OK -> Warning and Warning -> OK transitions (Warning State Alerts): Alert(s) to execute on an event (Event Alert): The form with the above sections will open if you select an alerting rule on the Settings -> Alerting Rules tab and click Edit button to the right of rules list. The form allows you to modify an existing rule. To create a new named alerting rule click the New button on Settings -> Alerting Rules tab. You need to set a rule name, all other sections are optional: the rule can be intentionally set empty. Add a required section by clicking on the “use custom” link on the right, select a named alert from the drop-down list, check needed lines and set the time values (for Down and Warning State Alerts) for: how soon after a state change the alert will be executed; how soon the alert should be escalated; how soon the alert should be repeated if the monitor stays in a ‘bad’ state too long. For escalation alert you can select an alert from appeared drop-down list, either the same as for the state change or another one. Select “” to use the same alert for state change and for escalation. You can disable escalation and recovery alerting by unchecking corresponding lines. To completely disable alerting for state transition or event click “do not report” link in the top right corner of the alerting section. You can also create a new alert (as described here ) directly from here by clicking on the ‘+’ icon on the right of the drop-down list, or edit a selected alert by clicking on the pencil icon on the right of the drop-down list as described here . Alerts and simple actions (blocks to construct an alert) are described in details below. In the sample below you can see the new alerting rule Down State Alerts section with an immediate alert, one escalation alert and two recovery alerts (Down->OK and long-term Down -> OK) configured. The Warning State Alerts section is not fully configured yet – the immediate alert is being selected from the drop-down list of named alerts: After the changes are complete click the OK button to save the named alerting rule. Now the rule can be assigned to any tree node on the node’s Alerting tab . There is a predefined alerting rule named Default Alerting Rule . This rule is assigned to the All Agents node by default after the first installation, and inherited by all the other tree nodes, e.g. monitors, by default: Hence you will receive immediate notification if a problem occurs without any additional configuration upon the installation is complete and monitors are created. You can add and modify named alerting rules on Settings -> Alerting Rules tab, and you can assign them to a monitor (or any other tree node) on the monitor (or other node) Alerting tab on Parameters/Results pane. Each new monitor inherits its alerting rule from its parent (host, application or device) by default, hence there is no need to specify a rule for each monitor separately. However, it is possible to set a custom rule for any monitor, host, host group or agent. A node, for example, a monitor, can use one of the three kinds of alerting rules: The rule inherited from the monitor parent (host, application or device), this is the default, One of the named rules, A custom rule specific to this monitor. In the sample below a monitor is configured to use an alerting rule inherited from its parent host: The root node (All Agents) can use either a named or a custom rule. In the sample below the All agents node is configured to use a named alerting rule: To assign and configure an alerting rule for any tree node, for example, for a monitor, use the node Alerting tab . You can change alerting rules inheritance mode for the node using the radio button area, select named alerting rule or set node-specific (custom) alerting rule on this tab. Global and Custom Alerting Rules Alerting rules can be named (global) and custom. The global ones have a name and can be used for any node in the tree view (a monitor, host, host group, agent or root). Select the menu Alerting > Alerting Rules (or press the Settings button on the toolbar), then select the Alerting Rules tab to invoke the form with a list of named (global) alerting rules. By default any new entity inherits its alerting rules from its parent. Inherited alerting rule can not be modified directly from the entity Alerting tab, you need either open the parent Alerting tab, or modify the rule itself (if it is a named rule) from Alerting > Alerting Rules menu. A named alerting rule can be assigned directly to any entity and can be inherited by this entity children. In the sample below you can see a named alerting rule assigned to a monitor. The drop-down list on the right of the selected checkbox item shows the rule name and the bottom part of the tab shows the Down State Alerts and Warning State Alerts sections of the rule: Named alerting rule assigned to a node can be partially disabled or overridden on place. After a named rule is assigned to a node (e.g. to a monitor), each of the rule three sections (Down State Alerts, Warning State Alerts and Event Alerts) can be in one of three states: inherited : use section from the rule for this monitor; use custom : use specific section for this monitor instead of the section from the rule; do not report : do nothing on this state change. You can switch a section between these states using the links at the top-right corner of the section description. Note that the rule itself is not changed if you switch its section state, you only change the way the rule is used: use the entire rule for this node, or use only a part of the rule to report the monitor state changes. You can disable any section of a named rule by clicking “do not report” link, for example, if you disable Down State Alerts section, the service will not send any alert if the monitor switches to/from Down state: Any disabled section can be added again by clicking “use inherited” link to add section inherited from named rule or “use custom” to add custom section that will override the inherited one: Any active inherited section can be overridden on place by a custom section: In the sample below the Warning State Alerts section of a named rule assigned to a monitor is overridden with a monitor-specific section. After the change is complete, if the monitor switches its state to Warning, the “Save logs” alert will be executed immediately: This is the final modified alerting rule for the monitor: Down State Alerts section of “Local Hosts Alert” named rule is used, and custom Warning State Alerts section is used: A custom alerting rule can only be set for a given node (a monitor, host, host group, agent, and root). The custom rule can be inherited by the node children, but can’t be assigned to another node directly. To create a custom alerting rule for the node check “Set alerts independently” on its Alerting tab. The custom rule template is similar to the Edit Alerting Rule form. If the node is a monitor its custom alerting rule template contains only sections available for the monitor type. For example, an Event Alert section is not available for the “SSH Remote Program or Script” monitor type: To save the changes click the Save button at the right-hand top corner of the pane. Alerts An alert is a set of simple actions : a command or command sequence the monitoring system will execute when a monitor state changes or an event occurs, and time schedules assigned to them. Alerts are used to construct alerting rules. All the alerts and the simple actions are provided in one common alert list that allows you to add a new alert or to review and modify an existing alert. Select the menu Alerting > Alerts (or press the Settings button on the toolbar) then select the tab Alerts to invoke a form with the alert list. Note that any change in an alert affects each alerting rule that uses the alert, and any change in simple action affects each alert that uses the simple action. On the image below you can see the Alerts tab with the list of alerts. The bottom part of the page shows the simple actions that form the selected alert, and their time schedule: On the Settings > Alerts > Alerts tab you can create a new alert and edit, copy or delete an existing alert. Select the alert you want to modify or delete and click the appropriate button. The New Alert form opens on clicking the New button. The only mandatory field is an alert name, the alert itself can be empty. Add any number of simple actions using the drop down menu Add on the right side of the form. To add a new simple action use Add > New Simple Action and then select needed simple action type from the drop down menu. After a simple action is added the New Simple Action form opens. The form allows you to configure the simple action: to set the recipient’s address, to modify the predefined message text (if available), and to set simple action name. After the New Simple Action is closed with OK button, a line with the newly created simple action is appeared in New Alert list and you can assign a time schedule from the drop-down list to it. Choose the item to allow the simple action will be executed 24/7. You can add a new schedule or modify an existing one my clicking on the “+” icon or pencil icon on the right of the drop-down list. The schedules are described in detail here . To add already created simple action use Add > Simple Action > Name of created simple action, you can also add all simple actions with their assigned schedules from another alert using Add > Alert > Name of existing alert. To save the new alert click OK button. Now it can be used by any alerting rule. All simple actions are described in detail here . The Edit Alert form opens on clicking the Edit button. Using this form you can: Change the current alert name; Add a simple action to the current alert; Remove a selected simple action from the current alert; Edit a selected simple action or its copy; Change time schedules assigned to simple actions. The Edit Simple Action form is similar to the New Simple Action Form and allows you to edit the message recipient and contents (if available) of a simple action, and to modify its name. After the changes are complete press the OK button to save the action. For example, you can create a named simple action ‘Send mail to ALL’ and configure the message to be sent to all the persons concerned: system administrator, project manager, etc. This simple action can be used in any number of combined alerts. In case an address is changed, you can replace it in a single place: in this simple action parameters. Disable alerting You can temporary disable all alerting. If the alerting is disabled you will not receive a notification if any monitor changed its state. To disable all alerting temporary uncheck the menu item Alerting > Enable alerting or uncheck Enable alerting in the system tray menu. If you disable alerting, a dialog opens, in which you should choose whether to enable alerting after a selected time interval automatically or not: You will see a warning indicator at the top of the Client and Web Interface window while alerting is disabled. Also, you can configure if regular notifications will be sent while alerting is disabled on the Settings > Alerts page of the Settings dialog. This option prevents you from unintentionally disabling alerting for a long time: Simple Action All simple actions are provided on the Settings > Alerts > Simple Actions tab, there you can create a new simple action and edit, copy or delete an existing simple action. The image below show the Alerts tab with the Simple Actions tab opened and a simple action selected. The bottom part of the page shows the content of the selected simple action: All simple actions available to construct an alert are listed below. Send an e-mail to specified recipients. Variables can be used in the message template, such as $MonitorName, $CurrentState, etc. (see the variables full list ), which allows using a single template for all and any state changes. Send an SMS message directly over the GSM modem or GSM cell phone attached to the computer. This action allows you to specify one or several phone numbers to send notifications to. To use this action you need to configure the GSM modem as explained here. By default, this action uses a short one-line message template to ensure that a single SMS message is enough to deliver the action. Send an SMS message over e-mail to a cell phone. This action allows you to select a provider from the predefined list; the e-mail address stub for this provider is created automatically and you should enter a valid user name or phone number into the bracketed placeholder. You can also specify the e-mail address manually. Make sure to enable the e-mail to SMS service for your phone number (this can be done on the provider’s web portal). By default, this action uses a short one-line message template to ensure that a single SMS message is enough to deliver the action. Send a message to an Internet pager. Supported IM clients are all the XMPP (Jabber) clients. Generally, you need two accounts to use this action: the first account represents IPNetwork Monitor (the sender) and you should enter a password for it in the monitor settings; the second account is the destination address for the message (you should start your IM client for this account to receive messages from IPNetwork Monitor). By default, this action uses a short one-line message template to ensure that a single line in the IM chat log is enough to view the action. Hence, the chat log looks like a common log file. Show a pop-up message. It is a standard pop-up balloon with the default notification connected to the application icon in the system tray. The message body can’t be configured. Send a message via Net Send. It is a standard window with a message, or a standard dialog with a message on a local or remote machine. The send method ‘NET SEND’ is not available on Windows Vista and later, hence the ‘MSG’ method should be used on all modern Windows versions. Run a program. This simple action starts a native binary or executes a script code in a language supported by Windows Scripting Host . The path to the file and its arguments (if any) should be specified. You can use a variable to specify program arguments. You can also specify a custom account for the program or script selecting the appropriate user credentials. One example: you can send alerts to Telegram using this simple action as explained in this article . Run a Python script This simple action starts a Python script using Python interpreter configured here in a Settings Dialog. The path to the script, its arguments and input to the script (if any) should be specified. You can also specify a custom account for the script by selecting the appropriate user credentials. This is necessary say when the script has to access LAN resources (monitoring service runs under Local System account by default and has no LAN access). Run a program remotely via SSH. It allows you to start any script or command on a given remote host over SSH. The command and credentials to access the remote host should be specified as explained here . You can specify program arguments using the variables. Play a sound file. This action plays a sound file either directly on the monitoring host or in the web browser. Supported audio format is MP3; .wav files are converted to MP3 ‘on the fly’ when you configure the action. In order to listen sound alerts in the web browser, you should: select the Play Sound in Web Browser checkbox in the action parameters open the Dashboard , Reports , or Alerts tab in the IPNetwork Monitor Web interface A sample ‘rooster cry’ sound can be found in the ‘mp3’ subdirectory of the IPNetwork Monitor data directory; a sample alert using this sound is already part of the default alerting rule but this rule is not enabled initially (not assigned to any state changes). Note: If you connected to the machine running IPNetwork Monitor via RDP (terminal services client), you will not hear audio alert generated by monitoring service. Set an SNMP value This action sets a given value via the SNMP protocol. The SNMP account used by this action should be granted write permissions for the variable to set. Changing some variables (sysName, sysLocation) may be prohibited by the SNMP agent even though they are formally writable. ‘ Value Encoding Type ‘ setting is normally auto detected based on the OID (using an SNMP GET request issued when you click on the ‘ New Value ‘ setting); however you can also select it manually; the default value for this setting is MIB lookup (auto detect) ‘ which instructs IPNetwork Monitor to determine the value type using the current set of MIB files so the SNMP variable should be defined by one of the MIB files. Send HTTP(S) request This action sends GET/POST request via the HTTP(S) protocol. Send an GET/POST request to the server with specified URL. Variables can be used in the GET/POST data, such as $MonitorName, $CurrentState, etc. (see the variables full list ), which allows using a single template for all and any state changes. HTTP(S) action has two types of validation: validation of response text and response code validation. If response doesn’t pass the validation, then action will be marked as a failed action in the log panel. This action can be used for integration with many web-based tools and applications. For example, you can post alerts to the following destinations: Slack channels: see this article HipChat rooms: see this article Stride rooms: see this article Microsoft Teams channels: see this article Send Push notification This action sends Push notification to one or several mobile devices. Note: IPNetwork Monitor needs internet connection to be able to send notifications. You need to install the IPNetwork Monitor Mobile app on your device and setup the connection to IPNetwork Monitor installation. We plan to add additional types of actions to IPNetwork Monitor, such as sending an SMS message via HTTP forms, and sending messages to Skype and other messengers. Sample Simple Actions This chapter contains a useful simple action sample. The following one-line script named log.bat writes state change messages to the text log file (assuming that the Cygwin toolkit is installed on the monitoring service host): C:\cygwin\bin\echo.exe %1 | C:\cygwin\bin\tee.exe -a c:\NetworkMonitor\logs\custom.log You should indicate the full path to log.bat as a Program name and specify the string to log using the Arguments setting of the Execute program action. Sample arguments might look like: “[$Time] ‘$MonitorName’ on ‘$HostName’ is in $NewState state” The following alerting rule is configured and assigned to a monitor. On each monitor’s state change the alert “Save logs” will be executed: The following simple action is used to construct “Save logs” alert: The script produces the following log: [28.05.2014 11:28:44] ‘File on remote standalone share’ on ‘linux1’ is in warning state [28.05.2014 11:29:19] ‘File on remote standalone share’ on ‘linux1’ is in ok state [28.05.2014 11:30:55] ‘File on remote standalone share’ on ‘linux1’ is in warning state [28.05.2014 11:31:33] ‘File on remote standalone share’ on ‘linux1’ is in ok state --- - [Alerting Tab | IPNetwork Monitor](https://ipnetwork-monitor.com/help/alerting/): Parameters/Results Pane: Alerting Tab ### Alerting Tab #### Parameters/Results Pane: Alerting Tab #### Try IPNetwork Monitor for Free ✕ Parameters/Results Pane: Alerting Tab Alerting Rules page. The Edit Alert form is described in detail here . You can assign a custom alerting rule to a given monitor (or host, etc.) by selecting the Set alerts independently radio button. The custom rule form is similar to the Edit alerting rule form. A custom rule can be inherited, but can’t be assigned to other entity directly. For any entity except for a monitor, you can reset inheritance mode for the entity’s children to the default Inherit alerts from … by clicking the Enforce return inheritance for children button: You can indicate whether only direct children or the whole subtree at any depth should be affected by the change. A confirmation dialog will appear that lists all the child nodes affected by the change; you can preserve custom alerting settings for some of them by unchecking these children. For example, if you click this button while a host is selected then all the host’s child monitors will lose their specific (custom or named) alerting rules and will get the rule inherited from the selected host. You can test alerting configuration on Testing tab for any given monitor. The Testing tab shows a list of simple actions that the monitoring service will execute on each state transition along with their time schedules and allows you to test how the monitoring service will execute them. Each section on this tab contains a list of alerts for one state transition, e.g. OK, Warning -> Down section lists alerts to be executed if the monitor switches to Down state. A section header shows a total amount of alerts for a corresponding state transition. You can open any section to view a full list of the alerts (the simple actions and their time schedules) by clicking on the section header. In order to check how the monitoring service will execute a section’s alerts you can either click the Test button on the section hearer, or open the section and click the Test button on the left of state change description. Note that the monitor will not change its state, and the alert will be executed immediately regardless of its time schedule. For example, if you click the first Test button in OK, Warning -> Down section in the example above, the monitoring service will execute 2 simple actions immediately: Send mail and popup. You can view the alerts execution log in the Test alerting dialog that appears after you click Test button. The log example below shows that the ‘Send mail’ alert fails due to an error in an SMTP server parameters. You can correct the SMTP server parameters on Settings -> Email Settings page and test the alert again to check the new parameters. Also, messages about the test alerts are added to the Logs pane: < mode > < string > [ credentials ] Program Mode: Run script This monitor reads the file named as the first script argument and searches for a particular string in the file. It has two execution modes: Mode ‘C’ (count): the script counts the total number of string occurrences in the file Mode ‘F’ (find): the script searches for the first string occurrence in the file and returns the first number it finds after this string. The credentials string, if present, has the same format as for the directory size monitor: domain, user name, and password separated by a colon. Since the monitoring service runs under a Local System account, it cannot access remote shared files by default and should pass valid user credentials to access a share. For example, you can use this script to parse the log file contents. The script can return the total number of particular messages, or q particular numeric value (that can be an error code). The following arguments instruct the script to return the total number of IPNetwork Monitor’s Web interface shutdowns: “C:\ProgramData\IPNetwork Monitor\logs\error.log” C shutdown HTTP Content Usage: ipnetwork_http_content.vbs < URL > < mode > < string > Program Type: Run script Program Mode: Standard This monitor makes an HTTP(S) request to the particular URL passed as the first argument and searches its contents for a particular string. It has two execution modes: Mode ‘C’ (count): the script counts the total number of string occurrences in the HTTP response. Mode ‘F’ (find): the script searches for the first string occurrence in the HTTP response and returns the first number it finds after this string. You can find many uses for this script. One funny example is weather monitoring. The following arguments instruct the script to return the current weather in London: “https://weather-broker-cdn.api.bbci.co.uk/en/observation/rss/2643123” F Temperature To determine a similar URL for your location, enter your city name at https://www.bbc.com/weather , and look at the resulting URL in the browser navigation bar. Please don’t schedule such HTTP requests too frequently; a polling interval of 1 hour should be enough in most cases. --- - [End User License Agreement | IPNetwork Monitor](https://ipnetwork-monitor.com/help/end-user-license-agreement/): IPNetwork Monitor End User License Agreement IPNetwork Monitor End User License Agreement IMPORTANT: THIS SOFTWARE END USER LICENSE AGREEMENT ("EULA") IS A LEGAL AGREEMENT BETWEEN YOU AND IPNetwork Monitor LLC. USE OF THE SOFTWARE PROVIDED WITH THIS AGREEMENT (THE "SOFTWARE") CONSTITUTES YOUR ACCEPTANCE OF THESE TERMS. READ LICENSE TERMS CAREFULLY BEFORE COMPLETING THE INSTALLATION PROCESS ### EULA (End User License Agreement) #### IPNetwork Monitor End User License Agreement #### Try IPNetwork Monitor for Free ✕ IPNetwork Monitor End User License Agreement IPNetwork Monitor End User License Agreement IMPORTANT: THIS SOFTWARE END USER LICENSE AGREEMENT (“EULA”) IS A LEGAL AGREEMENT BETWEEN YOU AND IPNetwork Monitor LLC. USE OF THE SOFTWARE PROVIDED WITH THIS AGREEMENT (THE “SOFTWARE”) CONSTITUTES YOUR ACCEPTANCE OF THESE TERMS. READ LICENSE TERMS CAREFULLY BEFORE COMPLETING THE INSTALLATION PROCESS AND USING THE SOFTWARE. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, DO NOT INSTALL AND/OR USE THIS SOFTWARE. BY INSTALLING, COPYING, OR OTHERWISE USING THE SOFTWARE PRODUCT, YOU AGREE TO BE BOUND BY THE TERMS OF THIS EULA. In case the EULA text supplied with your copy of IPNetwork Monitor software differs from the one published on IPNetwork product site, the EULA version on the product site takes precedence. IPNetwork Monitor LLC may supply the EULA text in languages different from English; the non-English EULA versions are only supplied for reference, and English EULA version always takes precedence. 1. LICENSE GRANT. IPNetwork Monitor LLC grants you a non-exclusive license to use the SOFTWARE in object code form as described in this EULA. 2. EDITIONS A. Commercial Edition IPNetwork Monitor LLC grants you a license to use one copy of the version of this SOFTWARE on a single computer. “You” means the company, entity or individual whose funds are used to pay the license fees. “Use” means storing, loading, installing, executing or displaying the SOFTWARE. You may not modify the SOFTWARE or disable any licensing or control features of the SOFTWARE except as an intended part of the SOFTWARE programming features. This license is not transferable to any other system, or to another organization or individual. B. Trial Edition You are granted the right to use the SOFTWARE without registration (Trial Edition of the SOFTWARE) solely for the purposes of evaluating the performance of the SOFTWARE for a period of no more than 30 days. If after that time continued use of the SOFTWARE is desired then the SOFTWARE must be registered with IPNetwork Monitor LLC subject to the terms as laid out in the registration information which can be found in the documentation accompanying the SOFTWARE. You are expected to use the SOFTWARE on your system and to thoroughly evaluate its usefulness and functionality before making a purchase. This “try before you buy” approach is the ultimate guarantee that the SOFTWARE will perform to your satisfaction. Support for Trial Edition is provided by email. C. Free Edition The Free Edition of the SOFTWARE may be installed on multiple computers for private and commercial use. The SOFTWARE may be transferred to third parties (e.g. on homepages or ftp-servers) as long as the SOFTWARE remains unchanged and is offered free of charge. A chargeable transfer of the SOFTWARE (chargeable download, CD in magazines) requires previous written permission by IPNetwork Monitor LLC. You may, free of charge: install and use SOFTWARE, copy, store, distribute and transmit, identical copies of this SOFTWARE to others. You may not: permit others to use this SOFTWARE unless they are properly licensed by IPNetwork Monitor LLC; copy SOFTWARE except as described above; sell or license copies of SOFTWARE to others; remove any proprietary notices or labels on SOFTWARE. SOFTWARE contains online help files. However, hard-copy documentation, email and other support are not available under this Free Version license. 3. MAINTENANCE AND SUPPORT CONTRACT. Object of the Maintenance and Support Contract is the maintenance and support of registered copy of the SOFTWARE. The customer will receive support by email for the duration of the Maintenance and Support Contract. The customer is granted the opportunity of downloading and installing the current version of the purchased the SOFTWARE for the duration of the Maintenance and Support Contract. The Maintenance and Support Contract starts from the date of purchase of the SOFTWARE and has a duration of 12 months and may be prolonged. 3.1. TECHNICAL SUPPORT 3.1.1. Technical support is provided exclusively via email. To request technical support, end user should either – send email message to support@ipnetwork-monitor.com – send support request via web form at /support.html 3.1.2. The subject matter of technical support through IPNetwork Monitor LLC is exclusively the IPNetwork Monitor installations that follow the setup and requirements described on IPNetwork Monitor website at /help/system-requirements-and-installation.html . 3.1.3. There is no obligation to provide technical support a) if the end user does not submit its query by using the means of communication designated by this EULA in paragraph 3.1.1, or b) if the end user does not communicate all of the information IPNetwork Monitor LLC requires to process the query in a reasonably processed and documented manner. 3.1.4. IPNetwork Monitor LLC processes technical support requests in the order received, using the below priorities (highest listed first): – requests from commercial license owners with active Maintenance&Support subscription – requests from commercial license owners with expired Maintenance&Support subscription – other support requests 3.1.5. Technical support operates from 8:00 AM to 5:00 PM (Washington time, USA) on business days (Monday through Friday, excluding US federal holidays). IPNetwork Monitor LLC does its best to provide first response within 2 hours during the mentioned time intervals. Subsequent responses to the same technical support incident are provided as soon as possible (that depends on the nature of technical support request being processed). 3.1.6. IPNetwork Monitor LLC can do custom (managed) setup and/or configuration of IPNetwork installation, as a paid service. Please contact us at support@ipnetwork-monitor.com for this service details. 3.1.7. IPNetwork Monitor LLC can provide your IT personnel with IPNetwork product training, as a paid service. Please contact us at support@ipnetwork-monitor.com for this service details. 3.1.7.1. Owners of Professional 1000 and/or Enterprise licenses are eligible for receiving initial (managed) setup assistance from IPNetwork Monitor LLC at reduced price. First 10 hours (for Professional 1000 license owners) or 15 hours (for Enterprise license owners) are provided free of charge. If you own one or more of the mentioned licenses, please contact us at support@ipnetwork-monitor.com for this service details. 3.1.8. Technical support is provided in English language. 3.1.9. IPNetwork Monitor may limit total time dedicated to handling end user technical support incidents to 3 to 9 hours per week per user, depending on incidents complexity and license type(s) end user owns. 3.1.10. The provision of extended technical support services (with availability outside the above referenced hours) or service levels (e.g. reaction and issue resolution times) shall require a separate agreement of the parties. 4. COLLECTING USAGE STATISTICS. Upon your consent, IPNetwork Monitor LLC may collect information on the usage of the SOFTWARE, such as utilized monitors and License Statistics. We collect and analyze this information to better understand the usage of our product, so that we can continue to develop a better product in accordance with the wishes of our customers. We do not share this information with third parties. 5. OWNERSHIP. The SOFTWARE is owned and copyrighted by IPNetwork Monitor LLC. Your license confers no title or ownership in the SOFTWARE and should not be construed as a sale of any right in the SOFTWARE. 6. COPYRIGHT. The SOFTWARE and all rights, without limitation including proprietary rights therein, are owned by IPNetwork Monitor LLC or its suppliers and are protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The SOFTWARE is licensed, not sold. You acknowledge that no title to the intellectual property in the SOFTWARE is transferred to you. You further acknowledge that title and full ownership rights to the SOFTWARE will remain the exclusive property of IPNetwork Monitor LLC and you will not acquire any rights to the SOFTWARE except as expressly set forth in this license. You agree that any copies of the SOFTWARE will contain the same proprietary notices which appear on and in the SOFTWARE. 7. REVERSE ENGINEERING. You agree that you will not attempt to reverse compile, modify, translate, or disassemble the SOFTWARE in whole or in part. 8. NO OTHER WARRANTIES. THE SOFTWARE PRODUCT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND. IPNetwork Monitor LLC DISCLAIMS ALL OTHER WARRANTIES WITH RESPECT TO THE SOFTWARE, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES OR LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY MAY LAST, OR THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THE ABOVE LIMITATIONS OR EXCLUSIONS MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS AND YOU MAY ALSO HAVE OTHER RIGHTS WHICH VARY FROM JURISDICTION TO JURISDICTION. 9. SEVERABILITY. In the event of invalidity of any provision of this license, the parties agree that such invalidity shall not affect the validity of the remaining portions of this license. 10. NO LIABILITY FOR CONSEQUENTIAL DAMAGES. IN NO EVENT SHALL IPNetwork Monitor LLC OR ITS SUPPLIERS BE LIABLE TO YOU FOR ANY CONSEQUENTIAL, SPECIAL, INCIDENTAL OR INDIRECT DAMAGES OF ANY KIND ARISING OUT OF THE DELIVERY, PERFORMANCE OR USE OF THE SOFTWARE, EVEN IF IPNetwork Monitor LLC HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT WILL IPNetwork Monitor LLC’ LIABILITY FOR ANY CLAIM, WHETHER IN CONTRACT, TORT OR ANY OTHER THEORY OF LIABILITY, EXCEED THE LICENSE FEE PAID BY YOU, IF ANY. 11. GENERAL PROVISION. This is the entire agreement between you and IPNetwork Monitor LLC, which supersedes any prior agreement or understanding, whether written, or oral, relating to the subject matter of this license. If any part of this agreement is found void and unenforceable, it will not affect the validity of the balance of the agreement, which shall remain valid and enforceable according to its terms. This agreement shall automatically terminate upon failure by you to comply with its terms. IPNetwork Monitor LLC, on its sole discretion, may modify this agreement in writing at any time. IPNetwork Monitor LLC 827 LACA ST Dayton, NV 89403, USA --- - [Getting Started with IPNetwork MCP API | IPNetwork Monitor](https://ipnetwork-monitor.com/help/getting-started-with-ipnetwork-mcp-api/): MCP API The IPNetwork Monitor MCP (Model Context Protocol) API opens up a new way to manage your network monitoring infrastructure. Instead of clicking through the UI, you can use AI-powered tools like Claude Code and Cursor to create hosts, configure monitors, set up alerting rules, and query monitoring data — all through natural language ### Getting Started with IPNetwork MCP API #### MCP API #### Table of Contents #### Configuring the MCP Server ##### Enabling MCP in IPNetwork Monitor ##### Making the MCP Server Accessible Remotely ###### Option 1: SSH Port Forwarding ###### Option 2: ngrok Tunnel #### Python Client Examples #### Using IPNetwork MCP API in Claude Code ##### Adding the MCP Server to Claude Code ##### Claude Code Example Session #### Using IPNetwork MCP API in Cursor IDE ##### Adding the MCP Server to Cursor ##### Cursor Example Session #### What’s Next #### Try IPNetwork Monitor for Free ✕ MCP API The IPNetwork Monitor MCP (Model Context Protocol) API opens up a new way to manage your network monitoring infrastructure. Instead of clicking through the UI, you can use AI-powered tools like Claude Code and Cursor to create hosts, configure monitors, set up alerting rules, and query monitoring data — all through natural language conversations. This guide walks you through enabling the MCP server, connecting it to your favorite AI coding tools, and running your first API calls. Table of Contents Configuring the MCP Server Enabling MCP in IPNetwork Monitor Making the MCP Server Accessible Remotely Python Client Examples Using IPNetwork MCP API in Claude Code Adding the MCP Server Example Session Using IPNetwork MCP API in Cursor IDE Adding the MCP Server Example Session Configuring the MCP Server Enabling MCP in IPNetwork Monitor The MCP server is built into IPNetwork Monitor but is disabled by default. To enable it: Open IPNetwork Monitor and go to Settings . Navigate to the MCP tab. Check Enable MCP Server . Configure the connection settings: Port — the TCP port the MCP server listens on ( 8888 by default). Binding address — the local network interface to listen on. Use 0.0.0.0 to accept connections from any interface, or 127.0.0.1 to restrict access to the local machine only. External hostname — the public hostname that MCP clients will use to reach the server. If you are using port forwarding or a tunneling service where the public port differs from the local port, specify it explicitly (e.g. abc.ngrok.app:443 ). MCP endpoint URL — a read-only field showing the final connection URL. Copy this URL to your MCP client configuration. Configure access tokens: Read-write token — grants full access to the MCP API, including creating and modifying objects. Read-only token — grants restricted access for viewing data only. Click Generate new to create random tokens. Use the read-only token for integrations that only need to query data. Regenerate tokens immediately if you suspect they have been compromised. Note: The MCP server shares the same SSL certificate configuration as the Web Interface. For HTTPS connections to work correctly, the domain name in your External hostname must match the Common Name in the SSL certificate. Making the MCP Server Accessible Remotely If your IPNetwork Monitor is running on a local network or behind a firewall, you’ll need to make the MCP server accessible to external AI tools. Here are two common approaches. Option 1: SSH Port Forwarding SSH port forwarding is the simplest and most secure option when you have SSH access to the machine running IPNetwork Monitor (or to a machine on the same network). Forward the MCP port to your local machine: ssh -L 8888:localhost:8888 user@your-ipnetwork-server This maps port 8888 on your local machine to port 8888 on the remote server. You can then connect your MCP client to: https://localhost:8888/mcp If IPNetwork Monitor is on a different host within the remote network: ssh -L 8888:192.168.1.100:8888 user@jump-server This forwards through jump-server to the IPNetwork Monitor at 192.168.1.100 . Tip: Add -N to the SSH command if you don’t need a shell session (e.g. ssh -N -L 8888:localhost:8888 user@server ). Option 2: ngrok Tunnel ngrok creates a public HTTPS tunnel to your local MCP server without requiring any firewall changes. Install ngrok from https://ngrok.com/download and authenticate: ngrok config add-authtoken YOUR_NGROK_TOKEN Start the tunnel: ngrok http https://localhost:8888 ngrok will display a public URL like https://abc123.ngrok-free.app . Update IPNetwork Monitor settings: Set External hostname to the ngrok URL (e.g. abc123.ngrok-free.app:443 ) Copy the updated MCP endpoint URL Use the ngrok URL in your MCP client configuration: https://abc123.ngrok-free.app/mcp Note: Free ngrok URLs change each time you restart the tunnel. For a stable URL, consider a paid ngrok plan or use SSH forwarding instead. Python Client Examples We provide a set of Python examples demonstrating common MCP API operations. The source code is available on GitHub: https://github.com/IPNetwork-Monitor-LLC/ipnetwork-mcp-examples The repository includes a reusable Python MCP client wrapper and five progressive examples: Example Description 01_basic_connection.py Connect to the MCP server and list available agents 02_create_host.py Create a host with Ping and HTTP monitors 03_alerting_setup.py Set up email alerts, schedules, and alerting rules 04_monitor_state.py Query current state, history, and statistics 05_bulk_operations.py Bulk create multiple hosts and monitors Quick start: git clone https://github.com/IPNetwork-Monitor-LLC/ipnetwork-mcp-examples.git cd ipnetwork-mcp-examples python -m venv venv source venv/bin/activate pip install -r requirements.txt export MCP_URL="https://your-server:8888/mcp" export MCP_TOKEN="your-read-write-token" python examples/01_basic_connection.py Using IPNetwork MCP API in Claude Code Claude Code is Anthropic’s CLI tool for AI-assisted software development. Adding the IPNetwork MCP server lets Claude interact with your monitoring infrastructure directly. Adding the MCP Server to Claude Code Using the CLI (recommended): claude mcp add --transport http ipnetwork-monitor \ https://your-server:8888/mcp \ --header "Authorization: Bearer YOUR_READ_WRITE_TOKEN" Or create a .mcp.json file in your project root: { "mcpServers": { "ipnetwork-monitor": { "type": "http", "url": "https://your-server:8888/mcp", "headers": { "Authorization": "Bearer YOUR_READ_WRITE_TOKEN" } } } } Tip: Use environment variables to keep tokens out of version control: json { "mcpServers": { "ipnetwork-monitor": { "type": "http", "url": "${MCP_URL:-https://localhost:8888/mcp}", "headers": { "Authorization": "Bearer ${MCP_TOKEN}" } } } } } Verify the connection by launching Claude Code and running /mcp to check the server status. You should see ipnetwork-monitor listed with its available tools. Claude Code Example Session Once connected, you can manage your monitoring infrastructure through natural conversation: You: List all agents and their hosts Claude: Let me query the MCP server. [Calls list-agents, list-children] Agent: Local Agent (ID: 1) ├── Servers │ ├── Web Server (192.168.1.10) │ └── Database Server (192.168.1.20) └── Network Equipment └── Core Switch (10.0.0.1) You: Create a new host "Production API" with IP 10.0.1.50 in the Servers group, and add a Ping monitor and an HTTP monitor checking https://api.example.com/health Claude: I'll create the host and monitors. [Calls create-host, create-monitor x2] Created: - Host "Production API" (ID: 15) - Ping monitor (ID: 42) — polling every 1 min - HTTP monitor (ID: 44) — checking /health every 2 min, depends on Ping You: Show me which monitors are currently down Claude: [Calls list-agents, list-children, monitor-state] All monitors are OK except: - Web Server > HTTP Check: DOWN since 14:32 (last value: timeout after 30000 msec) Using IPNetwork MCP API in Cursor IDE Cursor is an AI-powered code editor. Adding the IPNetwork MCP server lets Cursor’s AI assistant work with your monitoring configuration. Adding the MCP Server to Cursor Open Cursor and go to Settings > Tools & MCP . Click + Add new MCP server . Select Type: Streamable HTTP , enter the server URL and save. Or create a .cursor/mcp.json file in your project root: { "mcpServers": { "ipnetwork-monitor": { "url": "https://your-server:8888/mcp", "headers": { "Authorization": "Bearer YOUR_READ_WRITE_TOKEN" } } } } For a global configuration (available in all projects), create the file at: macOS: ~/.cursor/mcp.json Linux: ~/.config/cursor/mcp.json Windows: %APPDATA%\Cursor\mcp.json After adding the server, return to Settings > Tools & MCP to verify the connection shows a green status indicator. Cursor Example Session Open the AI chat in Cursor (Ctrl+L / Cmd+L) and interact with your monitoring setup: You: What monitors do we have on the my-win2019 host? Cursor: [Calls list-children for the host] The host "my-win2019" has 10 monitors: - PING — OK (1 msec) - CPU usage — OK (54%) - Free disk space on C: — WARNING (2%) - Web Interface — OK (5 msec) - Free physical memory — OK - Traffic speed total — OK (114 kbit/s) ... You: Set up email alerting for the Servers group: send alerts to ops@mycompany.com when any monitor goes down, with a 60 second delay Cursor: [Calls create-simple-action, create-alert, create-alerting-rule, then applies to host group] Done! Created alerting pipeline: 1. Email action → ops@mycompany.com 2. Alerting rule: 60s delay on DOWN, recovery alerts 3. Applied to "Servers" host group (inherited by all hosts and monitors) You: Create a script that checks all monitors and sends a summary to Slack Cursor: Sure, I'll query the current API structure first. [Calls list-agents, list-children, monitor-state] Here's a Python script using the MCP client library... What’s Next Browse the full IPNetwork MCP API Reference Manual for all available operations Explore the Python examples on GitHub to see common patterns Read the MCP protocol specification to learn more about the Model Context Protocol Visit ipnetwork-monitor.com for product information and downloads --- - [Global Settings dialog | IPNetwork Monitor](https://ipnetwork-monitor.com/help/global-settings-dialog/): The Settings dialog allows you to modify IPNetwork Monitor's general settings. These are administrator e-mail account settings, an access password and the default user account, system settings such as application paths and port numbers, web interface settings, database maintenance parameters, the global lists of reusable alerts, alerting rules, schedules and credentials, the global host maintenance ### Settings Dialog #### Try IPNetwork Monitor for Free ✕ The Settings dialog allows you to modify IPNetwork Monitor’s general settings. These are administrator e-mail account settings, an access password and the default user account, system settings such as application paths and port numbers, web interface settings, database maintenance parameters, the global lists of reusable alerts, alerting rules, schedules and credentials, the global host maintenance table, various monitoring and reporting settings, rediscovery parameters, SNMP settings, administrator’s tools, remote agent settings, and settings for the GSM modem(s) attached to the monitoring host. You can press the Apply button to commit modified settings without closing the dialog and the Cancel button to undo the changes that are not applied yet. The OK button accepts the changes permanently and the client application and/or monitoring service can be restarted for the changes on the System page to take effect. Table of contents Email Settings Access Password System Web Interface DB Maintenance Monitoring Alerts Alerting Rules Mobile Devices Reporting Maintenance User Credentials Rediscovery SNMP Admin Tools GSM Modems Remote Agents Schedules MCP Index Email Settings Next> --- - [Glossary | IPNetwork Monitor](https://ipnetwork-monitor.com/help/glossary/): The following terms and abbreviations are used in this help file, monitoring client, Web interface, and IPNetwork Monitor online content. The terms are ordered alphabetically. TermExplanation Agent or Remote Agent A specific service module that can be installed on a separate host (not on the main monitoring host) and can be connected with the monitoring ### Glossary #### Try IPNetwork Monitor for Free ✕ The following terms and abbreviations are used in this help file, monitoring client , Web interface , and IPNetwork Monitor online content. The terms are ordered alphabetically. TermExplanation Agent or Remote Agent A specific service module that can be installed on a separate host (not on the main monitoring host) and can be connected with the monitoring service. Remote Agent allows you to monitor resources in partially isolated networks that can’t be accessible by the main monitoring service directly. The main monitoring service can be referred to as Local Agent. See a detailed description: Remote Agents . Alert A command or command sequence to be executed by the monitoring system. Alerts are linked to monitors via alerting rules that define system behavior on resource state changes or events . Alerts themselves are not associated with state changes and/or events. An alert example is: send an e-mail message to Administrator. There is a global list of named alerts on the Settings dialog Alerts page. Alerting Rule A set of alerts linked to monitor state transitions or events that trigger an alert in the set. If a monitor changes its state or causes an event, the corresponding alert is triggered. An alerting rule with two alerts example is: send an e-mail message to administrator for state changes to Warning and Down and show a pop-up message for each state change. You can combine as many alerts as you wish in a given alerting rule. Alerting rules define how the monitoring system responds to monitor state changes and events. The framework is flexible: there is a list of global alerting rules in the Settings dialog, and you can assign any alerting rule to a given monitor. Also, a monitor can inherit an alerting rule from its parent host. Further, a custom alerting rule can be assigned to a given monitor. Application A tree node: a result of applying an application template to a given host. It contains all the monitors from the template applied to the host and, possibly, monitors added by user. See a detailed description here . Device A tree node: a result of applying a device template to a given host. It contains all the monitors from the template applied to the host and, possibly, monitors added by user. See a detailed description here . Event A monitor can trigger an event even if its state doesn’t change. For example, the SNMP Generic Trap monitor listening for a specific trap turns to OK state after getting the first trap and then it triggers an event without changing the state every time it gets the next trap. You can assign alerts to an event the same way as for state changes; for instance you can get the system to send an e-mail message to Administrator. Host A device with an IP address assigned. A host is a set of resources that can require monitoring . Host Group A group of hosts of the same kind. For instance, a Servers group contains all server hosts configured for monitoring. If you add a host to the monitoring system manually, you can select a host group via a drop-down list on the New Host page. On network discovery , hosts are placed in either Servers or Desktops and Notebooks groups by default. To change the host group afterwards, you can use the Change button in the Name and Grouping section of the Main parameters tab for the host. In order to create a new Host Group, select an Agent (Local or Remote) and use the New Host Group entry from its context menu. It is possible to create nested host groups to organize hosts the way you need. Logs Diagnostic messages produced by system components. A monitoring client and monitoring service write log messages to the database; you can access them from the monitoring client using the Logs Pane . There are two kinds of messages: system messages and monitor-specific messages. The Apache Web server that provides the system’s Web interface writes standard access.log and error.log files to the logs subdirectory of the IPNetwork Monitor directory in the common application data directory such as C:\ProgramData\IPNetwork Monitor\logs on Windows Vista or Windows 7 or later versions. The monitoring service writes the service.log file to the same directory. Log files are rotated according to logging settings . Maintenance A specific time period when specified host resources are considered unavailable but do not generate alerts. By default, hosts are monitored permanently (no maintenance interval is configured). See a detailed description here . Monitor A logical system unit that monitors a certain resource . A monitor accesses a resource on a particular host in accordance with monitoring parameters such as Polling Interval , Port Number , and so on. A monitor also has parameters that specify how to distinguish resource states and what alerts should be triggered on state changes or events. Monitor Type A group of monitors for the same resource kind. For example, the POP3 monitor type logically groups all POP3 monitors. Monitor Category A group of monitor types for the same target area. For instance, the Mail monitor category logically groups SMTP, POP3, and IMAP monitor types. Monitoring A periodic process that checks resource availability and performance. Monitoring Client This component is a Windows GUI application available from the Program Files menu and through the Desktop icon. It is used to browse and change the monitoring system configuration and to view reports, graphs, and logs. It is described here . Monitoring Service This component is a Windows service that performs network discovery, monitors local or remote network resources, delivers notifications, executes alerts, writes logs, and collects monitoring data. It is described here . Network Discovery An automated search for hosts and their particular resources. It can be started either manually or on schedule (periodic rediscovery) as explained here . Poll A single resource check. Monitors do polls at certain intervals; you can also do a poll manually from the monitoring client. Reports HTML pages generated by the reporting module on the Apache Web server. You can access summary reports for default reporting period (usually 24 hours) from the monitoring client . You can access Summary , Problems and Trends reports for any period from the Web interface . In addition, you can receive Daily , Weekly and Monthly Summary, Problems and Trends reports over e-mail as explained here . Resource An entity that is subject to monitoring . Typical resources are services provided by hosts (HTTP service, SMTP service, Database servers, etc.), files, directories, physical hardware components (CPU, memory, network cards), and so on. Schedule It is a named timetable that defines weekly maintenance periods and repeating alerts . A schedule can be created and configured on the Schedule Settings page . Settings Parameters that define monitoring system behavior. Global settings accessible through the Settings dialog apply to the entire system. Individual parameters for monitors, hosts, and monitor groups are available in the Main parameters , State conditions and Alerting tabs of the Parameters/Results Pane. Monitors have a number of parameters that control their behavior. Hosts, monitor types, and other monitor groups also have parameters that can be used as templates for individual monitor parameters, as comments for Web reports, etc. State A monitor attribute that depends on monitoring results and configuration settings. A monitor can be active or inactive; active monitors are polled periodically and can be in one of the following states: OK , Warning , Down , Unknown . Inactive monitor states are: Stopped , Stopped by Dependency , on Maintenance or Discovered (not started after being discovered). The monitor states are described here . Note that the terms monitor state and resource state are synonyms and can be used interchangeably across the documentation. State Change or State Transition An event that takes place when a monitor state changes in the monitoring process. The most important state changes are listed below: Down : switch to a Down state from any other state Warning : switch to a Warning state from any other state OK : recovery from one of the ‘bad’ states ( Down , Warning ) back to OK . You can assign alerts to any of the three state changes above; for instance, you can get the system to send an e-mail message to Administrator on any state change. No state change occurs if resource monitoring has been canceled while in a certain state and then resumed (either manually or due to Maintenance or by Dependency) because the previous ‘active’ state of the resource is remembered. State Conditions The rules that define when a given monitor should switch from one state to another are named State conditions . Each state condition consists of several (one or more) sections , and each section contains a single rule, for example, a list of the values that are accepted as a monitored service response codes. See a detailed description here . Template A set of preconfigured monitors with state conditions. A template can be applied to a given host, so that all the template monitors will be created on the host at once. See a detailed description here . Template Attachment A file attached to template. Attachments can be of two types: SNMP MIBs and all other files, for example, scripts or programs. Content of attachment file is embedded in template. Attachment files will be placed either in predefined standard directory – those attachments are called standard , or they can reference some other files on a file system – such attachments are called custom . Those attachments can be referenced from template monitors. For example, you can create script for monitoring some resource and add this script as template attachment. Then you can refer to this script in Script or Program template monitor or use path to this template attachment in some monitor setting. Deployment of Template Attachment It is a process of creating template attachment on file system. When template is added to IPNetwork Monitor, it is stored in database together with its attachments. Those attachments that are designated to be placed in predefined directories (standard attachments), are created on file system as well. And attachments with nonstandard paths (custom attachments) are not created on file system, unless “Deploy” flag is set manually. User Credentials It is a platform-specific set of user credentials that the monitoring service uses to access a resource on a target host: Domain/Username/Password for resources on a Windows host, Username/Password for resources on a UNIX-like host (or other resources that require a Username/Password pair, such as SMTP or POP3/IMAP mail servers), and a Version/Community or Version/Username/Password/Encryption key for SNMP resources. See a detailed description here . Web Interface This component is a URL available from the Program Files menu; the Apache Web server provides access to this URL. The Web interface allows you to view reports and graphs showing the current system state or monitoring results for any time interval, from any Internet browser-enabled device including mobile devices. It is described here . --- - [Group Properties | IPNetwork Monitor](https://ipnetwork-monitor.com/help/group-properties/): Main parameters Tab: Group Entity Parameters Host Parameters A host has several parameter sections. Some host parameters provide the default values for their child monitor and template parameters. The Name and Grouping section contains a human-readable host name that is used in all kinds of reports. This name can be changed but should be unique ### Group Parameters #### Main parameters Tab: Group Entity Parameters #### Try IPNetwork Monitor for Free ✕ Main parameters Tab: Group Entity Parameters Host Parameters A host has several parameter sections. Some host parameters provide the default values for their child monitor and template parameters. The Name and Grouping section contains a human-readable host name that is used in all kinds of reports. This name can be changed but should be unique throughout the monitoring system. The host’s parent nodes (Agent and Host Groups) are listed in this section as clickable links. The host can be moved to another group using the Move… button: You can assign custom icon for the host using the dropdown control next to Icon . By default, a host uses an icon defined for its host group. It is possible to upload and use your own icon(s). The Host Definition section contains parameters used to identify a host within the monitoring system by providing its DNS hostname and/or IP address and to specify whether the DNS name or the IP address should be used to poll the host’s resources. Both parameters can be changed. In addition, this section contains the Admin web interface – a URL that is used to address the host via the Admin Tools > Device web interface drop-down menu. This parameter can be changed, too. The Host Maintenance section contains the Maintenance Period parameter that you can use to indicate temporary host unavailability due to periodic or one-time maintenance. To edit this parameter click the Edit button, and modify the values in the Maintenance Period editor: The Polling interval section defines the default frequency of monitor state checks (polls) for all the host’s child monitors. A minimum interval is 15 seconds. The default value is set to 1 min. and can be changed. The available units are: seconds, minutes, hours, days, weeks, and months. By default, this section is inherited from the host’s parent host group, but can be set to be host-specific and can be modified after that. Note that the changed parameter will be immediately applied to all the host children that inherit it. Also, you can set the host children to inherit this section immediately by clicking the Enforce return to inheritance for children button: The Dependency settings section defines the default Dependency settings section for all the host’s (or any other entity’s) child monitors. The state of a current monitor depends on the state of the monitor specified in this section: if the specified monitor changes its state say to Down (as in the example below), then the current monitor immediately changes its state to Stopped by dependency . It is possible to indicate dependency from PING monitor on current host (this is the default and reasonable choice because it makes no sense to poll host resources when it is not reachable), or to indicate a particular monitor: You can use the following conditions to create dependencies: For example, you can configure some monitor to enter Warning state when important operation such as regular backup starts, and define other “guard” monitor that depends on the first one and stops as soon as that monitor is not in Warning state. This way, “guard” monitor will only be active when backup operation is ongoing. Monitors on remote agents also may depend on remote agent connection state. By default, a host section is inherited from its parent host group, and hence, can not be edited directly. You need to either edit the parent parameter, or make this parameter host-specific by unchecking the Inherit from checkbox, and editing it directly. Also, you can set the host’s children to inherit this section immediately by clicking the Enforce return to inheritance for children button. The Regular reporting section allows you to send host (or any other entity) status reports by email on a regular basis (daily, weekly or monthly). By default, the Notes (in reports) field contains the monitor creation date and can be modified. By default, the Report by email filed is empty. Click the Edit button to open the report schedule editor window: The Credentials section contains drop-down menus to select user credentials the monitoring system uses to access resources on this host. Each kind of credentials (Windows-like: Domain/User/Password, UNIX-like: User/Password and, SNMP: Version/Community) can be selected independently. By default, a host inherits the credentials parameters from its parent host group. You can set the host’s children to inherit this section immediately by clicking the Enforce return to inheritance for children button. The Selected Objects and their Contents section contains a set of objects currently selected in the Tree View pane. Only visible objects are counted in the selection. If a group object (an template, host, host group or monitor category) is selected, then all its visible children such as hosts, monitor types, and monitors are also considered to be selected. The section allows you to view a brief summary status of the selected objects. Template Parameters A Template has standard parameter sections: The Name and Grouping section contains a changeable template name and a clickable link to its parent host, host group and agent. The Template Monitors section contains a list of all the monitors included in the template. The table shows if a monitor is enabled or disabled and if the monitor is a part of the template or added to the template by the user. You can enable or disable the template monitors by checking/unchecking them in this table. A disabled monitor becomes hidden (not deleted), all its data is saved, and it can be enabled at any time. Polling interval Dependency settings Regular reporting Credentials Selected Objects and their Contents Host Group Parameters A Host group ( Servers , Network Equipment , Desktops and Notebooks , Printers and UPS , Miscellaneous , and any custom group you may have created) has standard parameter sections: The Name and Grouping section contains a changeable group name and a chain of clickable links to its parent nodes (Agent and Host Groups). You can move the host group to another location using the Move… button. You can also select an icon that will be applied by default to all hosts and nested host groups within the group. By default, nested host groups use parent group icon and top-level groups use some specific icon. Note : you can browse for a custom icon which will be scaled and copied to a standard directory, $IPNetworkDataDir/icons . Polling interval Dependency settings Regular reporting Credentials Selected Objects and their Contents Agent Parameters Parameters for any Agent, whether local or network, contain the following sections: The Name and Grouping section contains a changeable Agent name Polling interval Dependency settings Regular reporting Credentials Selected Objects and their Contents Root Entity Parameters The root entity settings contain the following sections: Polling interval Dependency settings Regular reporting Credentials Selected Objects and their Contents Monitor Type Parameters Most of the monitor type parameters provide the default values for corresponding monitor parameters. The network discovery process uses these default parameters when it creates new monitors during discovery. You can adjust them before starting discovery (for example, set specific credentials for your mail servers). The default parameters are also used when monitors are created manually. The monitor type parameter sections are listed below: The Monitor Definition section contains the default values for all the monitor-type specific parameters and allows you to modify these parameters Regular reporting Selected Objects and their Contents Monitor Category Parameters The Monitor category parameters contain only two standard sections: Regular reporting Selected Objects and their Contents Monitor State Parameters The monitor state parameters contain only two standard sections: Regular reporting Selected Objects and their Contents --- - [GUI Overview | IPNetwork Monitor](https://ipnetwork-monitor.com/help/gui-overview/): All the client GUI monitoring configuration controls, monitoring results, and logs are available on one screen. This design is intended to save your time. Typically, when you change the settings you expect to see the immediate effect in monitoring results, and when you see a problem in the monitoring results you might want to adjust ### GUI Overview #### Try IPNetwork Monitor for Free ✕ All the client GUI monitoring configuration controls, monitoring results, and logs are available on one screen. This design is intended to save your time. Typically, when you change the settings you expect to see the immediate effect in monitoring results, and when you see a problem in the monitoring results you might want to adjust the monitoring parameters or alerts. Below is the default GUI layout. The GUI components are described below. Menu The menu allows you to configure the GUI itself as well as the network monitoring and reporting process, to print HTML reports, to register the product, and to access help pages and online technical support. Please note that some menu actions have keyboard shortcuts defined. Toolbars The standard toolbar provides navigation facilities and access to the most frequently used functions. You can navigate over the monitoring system configuration using the familiar pair of Back and Forward buttons and a drop down list of recently visited places or open the Web interface’s Dashboard tab that shows your system’s summary status by clicking the “Web Interface” button. The following functions are also available through this toolbar enabling you to: create / delete a new host group / host / monitor, discover hosts and resources on the network, undo / redo changes, access the global setting configuration. The monitor control toolbar allows you to handle the monitor tree and to perform actions on selected monitors and monitor groups. You can expand a current monitor tree, expand only problem nodes, collapse the tree, filter particular monitor states out, search for a particular host or monitor, start, stop, and poll monitors and monitor groups, and add monitors to the Favorites view. You can also launch external Admin Tools such as a remote desktop or SSH client. This page provides more information on configuring them. There are keyboard shortcuts for Start/Stop/Poll now actions: Ctrl+1 (Start), Ctrl+2 (Stop) and Ctrl+3 (Poll now). There are small toolbars on the Logs Pane and on Report Tab on Parameters/Results Pane as well; they are described below. Tree View The Tree View pane provides different views of monitored objects and allows taking a quick glance at the system status. It contains two tabs: The Main view tab provides monitoring system Tree view organized by the remote agent, host group, and host. This tree provides an inheritance path for most of the configuration settings so it has its own tab. The View: tab contains six other trees: one organized by the monitor categories and types, the other one organized by current monitor status, the third one containing newly discovered monitors, the fourth one contains favorite monitors, the fifth one organized by templates and template categories and the last one following the monitor dependency chains. You can select one of them using the dropdown menu on the tab. Each tree node has an icon indicating the worst child monitor state in the node. Changing the focus in a Tree View will result in reloading the contents of all the other client panes on the screen. The most frequently used actions are available from the Tree View pane context menu that appears when you right-click a selected monitor or group. You can select several objects in a Tree View by holding Ctrl and clicking on them with the mouse. In this case actions will be applied to the selected items and all their visible children. For example, if you select two non-empty hosts and press the Start button, then all visible monitors of these hosts will be started. Or if you press the Delete button, then the two hosts and all their visible monitors will be deleted. Note that if a monitor is not visible in the tree (filtered by name or state), then the action will not be applied to that monitor. There are the Search String text field and Filter by State or Agent button at the top of the Tree View window. They allow you to filter monitors in the Tree View pane. Main parameters Tab/State conditions Tab/Alerting Tab The Main parameters Tab, State conditions Tab , and Alerting Tab are used to configure the monitoring process. They display all general parameters of an object currently selected in the Tree View and allow you to edit these parameters. These tabs contain several sections specific to the object type: either a single monitor, or a group entity: host, host group, agent, and root. The Main parameters Tab also contains parameters for monitor types, categories, and monitor status nodes. The other tabs for these types of nodes are empty because they do not participate in inheritance of monitoring parameters. Report Tab The Report Tab displays an HTML report for a currently selected monitor or group. When a monitor is selected, a detailed report including a performance graph and all state changes of this monitor is displayed (the default report period is the last 24 hours and may be changed in the Settings dialog). When a monitor group is selected, its summary report is shown. You can navigate the reports you have loaded using the Back and Forward buttons on the toolbar on Report Tab, Refresh a report, and open the Web interface with this report loaded using the Open in Browser button. When you navigate the HTML links in a report or use the Back / Forward buttons, not only the Report tab content is changed to display data for the new monitor or group but all the other panes are updated too. Logs Pane The Logs Pane provides access to log messages stored in the database. You can choose to display either system messages or monitor state change messages, or both in the Logs Pane using its toolbar. The state change and event records are filtered in accordance with the currently selected monitor or group; only messages related to the current selection are shown. Log records for hosts and monitors contain hyperlinks; by clicking on them you select a corresponding object in the Tree View pane and all the other panes. Settings The Settings dialog provides access to settings that are outside the Parameters/Results View scope. These are administrator e-mail account settings on the E-mail page; the user’s access password on the Access Password page and default account and user credentials sets on the User Credentials page; System settings such as application paths and port numbers, global lists of reusable Alerts and Alerting Rules , the global Maintenance table, various Monitoring and Reporting settings, network Rediscovery parameters, SNMP monitoring parameters, commands to start various Admin Tools , GSM Modems settings, Remote Network Agents settings, and Schedules settings. Some settings from E-mail and User Credentials pages can be entered in the Welcome Wizard that opens when you start the client for the first time. Additional indicators Indicators appear in the topmost area of the main window (the indicator area) when Network Discovery or Rediscovery is carried out, or when a Remote Network Agent upgrade is in progress. When Network Discovery or Rediscovery is running, a progress bar appears in the indicator area to show its status. You can stop the Network Discovery execution by pressing the Stop button to the right of the status bar that appears when the discovery begins. When a Remote Network Agent upgrade is in progress, an upgrade log is displayed in the indicator area. You can close it when the upgrade is over. While alerting is disabled, a warning bar is displayed in the indicator area. Click the Enable alerting button to enable alerting. --- - [Templates Dialog | IPNetwork Monitor](https://ipnetwork-monitor.com/help/gui-properties-templates/): The Templates dialog allows you to manage application templates defined in the system configuration: import a template from an XML file; export a template to an XML file; edit, rename and copy a template; configure a template monitors list; set how a template is applied during discovery; delete a template; upgrade a template applications to ### Templates Dialog #### Try IPNetwork Monitor for Free ✕ The Templates dialog allows you to manage application templates defined in the system configuration: import a template from an XML file; export a template to an XML file; edit, rename and copy a template; configure a template monitors list; set how a template is applied during discovery; delete a template; upgrade a template applications to the latest version; an find a detailed description of the templates framework here . Templates list The left pane lists all the application templates defined in the system configuration along with their short descriptions. Templates are marked by different colors. The system templates are dark gray, the user-defined templates are black. All the standard templates are divided into categories by their target applications, services or resources. You can add your custom template into any category. The right pane shows the template parameters: Name, short description and version: The template name must be unique within the monitoring system. Template Monitors section allows to enable or disable the monitors. The disabled monitors are not created if the template is applied to a host manually (via New Monitor Wizard). You can configure how to process disabled monitors during discovery in the Discovery Settings section. By default, only few monitors are enabled for each standard (predefined) template. You can review the predefined templates in this dialog and configure them at any time. Find field allows to filter the monitors list by a keyword. Enable all checkbox allows to enable/disable the entire list. Create or reuse PING monitor on the host checkbox allows to create an additional PING monitor on the host (if there is no one) or reuse the existing PING, and set the application monitors dependency to this PING monitor. Note that not all the parameters of a predefined template can be configured. In the sample above the parameter Create or reuse PING monitor on the host can not be configured. All the parameters of a the user-defined template can be configured at any time. Discovery Settings section allows to configure how the discovery process should find and apply the template. Template can be used in network discovery checkbox allows to set if the template will be used in the automatic network discovery. Match monitor drop-down list allows to select the specific monitor that the discovery process uses to determine if this template should be applied to the host. By default, the discovery process tries to create the match monitor on the host, and if the monitor switches to OK state, the discovery process applies the template to the host. This parameter can’t be configured for the standard (predefined) templates. Use Match monitor only for network discovery checkbox if turned on specifies that the Match monitor will only be used temporarily for the discovery process and is not a part of the application. Discover application when: radiobutton area allows to specify when the template should be applied to the host during discovery. Mutually exclusive group checkbox/drop-down list allows you to select (or define) a template group that limits the discovery process: if one template from the group is already discovered on a host, then all other templates from this group will be skipped. Create monitors not detected by discovery checkbox/radiobutton area specifies what to do with the template monitors that are not discovered. A checkbox instructs IPNetwork to create such monitors, and radio buttons indicate which monitors to create. Such monitors look and behave differently from actually discovered monitors: if you choose not to start monitors added in course of discovery, such “not found” monitors are created in Stopped state, rather than Discovered state; if you choose to start monitors, they will remain in Stopped state as well because otherwise they would switch to Down state immediately after starting. When such monitors are added, a message in the log panel indicates the reason for creating them. Attachments section allows to add, remove or edit attachments in template. Number of attachments in current template is shown in the header of Attachments section. Each attachment takes one row in the table with the following columns: Type is one of predefined attachment types: SNMP MIB for SNMP MIB files; Script etc. for all other attachments. Path shows where attachment will be placed and how it can be referenced from monitor settings. Deploy check box can be used to enable or disable deployment for attachments with custom path. Attachments with standard paths ( “$AppFiles” and “$IPNetworkDataDir/mibs” ) are deployed automatically. This column contains button for copying, moving or renaming attachment. Last column contains button for removing attachment. After making changes to the list of attachments you will have to save updated template or abort changes before leaving this template or closing Templates dialog. If you changed attachments in custom template then before saving it you will be prompted to increase template version with a dialog: If you answer with “Yes” then template will be saved in database with new version and old version will be marked as outdated, and if you answer with “No” then it will overwrite existing template. If you press a button for editing template attachment, you will be presented with the following dialog: There you can select new name and path for this attachment and also choose if you want to delete original file after copying. If you press a button for removing template attachment, it will be removed from template. You can add new attachments to the template by pressing Add button in Attachments section. You then will be presented with the following dialog: There you can choose type of attachment, select one of existing files from file system and also decide if you want to copy this attachment to standard directory. Standard directory for scripts is “$IPNetworktDataDir/templates/