Complete network monitoring

  • More than 200 types of meters  that can cover all aspects of network monitoring
  • Monitoring of availability time/downtime
  • Monitoring of bandwidth by using SNMP, WMI, NetFlow, sFlow, jFlow, Packet Sniffing
  • Monitoring of applications
  • Monitoring of virtual servers
  • SLA monitoring
  • QoS monitoring (i.e. to monitor VoIP)
  • Monitoring of configuration
  • LAN, WAN, VPN and multiple sites monitoring
  • Recording of extensive events
  • Support of IPv6
  • Agentless monitoring (optional agents allow a more in-depth monitoring)

Detailed reports

HDCE Network Monitor includes vast report functions

  • Reports in HTML or PDF formats
  • Historical date exported such as HTML, XML, CSV
  • More than 30 models
    • Detailed graphs and tables for each probe
    • Availability/downtime (% and seconds)
    • Successful requests/failed
    • Top 100, usage of bandwidth
    • Top 100, usage of CPU
    • Top 100 ping time
    • Top 100 disk space
    • Top 100 availability/downtime
    • Other

Monitoring packages
Version Check interval Number of meters Notification system Price
Standard 3minutes 20 emails/SMS $3.99

Pro Best seller

2 minutes 40 emails/SMS $8.99


1 minute 150 emails/SMS $49.99

The benefits of network monitoring

As a business, when we invest time and money in our infrastructure, we expect that everything will work perfectly. However, we also know that such an innovative technology has limitations.

At HDCE, we make sure that your investment remains profitable. Thanks to the monitoring of your infrastructures, you are aware of the slightest problem. This tool insures not only the efficiency of your entrepreneurial activities, but brings you peace of mind.
In addition to a continuous real-time surveillance of all your applications, remote monitoring lets you save precious time and support fees and thus increases your profitability through continuation of your activities.

Remote monitoring allows real-time verification of your systems and warns you of the slightest deficiency (failure, slowing-down, error in the proactivity of systems, parts replacement). It then allows you to avoid any disaster or usual technological constraint that could stop your activities for an undetermined period. Remote monitoring can be used for the following applications:

  • Servers
  • Networks
  • Workstation
  • Peripherals
  • Web sites
  • Application systems

This system can also provide you with important information such as response time, rate of success, rate of failure, etc.

What data can the systems provide?

The first diagram represents the response time of a page. For example, when an user clicks on a page, the best delay for a page to open is 647 millisecond. This diagram shows that the page opens in 3.824 msec (3 seconds), which is too long.


As for the second page, the table shows several values such as moments when all is active and downtime periods.


Can we benefit from HDCE’s remote monitoring services even if we are hosted elsewhere?

In most cases, remote monitoring services are used for external hosting.

Planned downtime and unplanned downtime can be differentiated. Typically, planned downtime results from maintenance which disrupts the system’s operation and generally cannot be avoided with the design of the installed system. Planned downtime could include corrections of system software needing to be restarted or a system being subjected to a configuration revision that can become effective only after a reset. Generally, programmed downtime results from a logical management of events initiative. Unplanned downtime is the result of a physical event, such as hardware or software failure or an irregularity in the environment. Unplanned events of unavailability include power failures, failure of CPU or RAM components (or other defective hardware components), shut-off due to ever-heating, logically or physically cut-off network connections, breach of security or other applications, middleware or failure of operating system.

Numerous computer sites exclude planned downtime when calculating availability presuming that it has little if no impact on users. In so doing, they cannot pretend having a high availability. Systems having an actual high and continuous availability are relatively rare and more expensive than most. For certain systems, planned maintenance has no impact, for example, a business closed at night. This way, maintenance is programmed when all employees are away and there are no entrepreneurial activities.

Calculations in percentage

Availability is generally expressed as a percentage of the availability for a given year. The following table shows authorized downtime for a certain percentage presuming that the system must function at all times. It shows the translation of a given percentage of downtime of a system into the corresponding downtime expressed in years, months or weeks.


Availability % Annual downtime Monthly downtime * Weekly downtime
90 % 36,5 days 72 hours 16,8 hours
95 % 18,25 days 36 hours 8,4 hours
97 % 10,96 days 21,6 hours 5,04 hours
98 % 7,30 days 14,4 hours 3,36 hours
99 % 3,65 days 7,20 hours 1,68 hours
99,5 % 1,83 days 3,60 hours 50,4 minutes
99,8 % 17,52 hours 86,23 minutes 20,16 minutes
99,9 % 8,76 hours 43,8 minutes 10,1 minutes
99,95 % 4,38 hours 21,56 minutes 5,04 minutes
99,99 % 52,56 minutes 4,32 minutes 1,01 minutes
99,999 % 5,26 minutes 25,9 seconds 6,05 seconds
99,9999 % 31,5 seconds 2,59 seconds 0,605 seconds
99.99999 % 3,15 seconds 0,259 seconds 0,0605 seconds

© HDCE, 2015 - Tous droits réservés/ Copyrights
Termes et conditions