Subscribe to our Newsletter!
By subscribing to our newsletter, you agree with our privacy terms
Home > IT Monitoring > The IT monitoring market: suites and business models
July 20, 2023
If a company is dependent on its IT – which affects practically every company today –- the availability and performance of the IT, that is, the infrastructure and the network, must be constantly monitored. This is the only way to intervene immediately in the event of disruptions before they cause serious damage. And they will do if they are not detected, localized, and remedied in good time.
This somewhat divergent relationship with monitoring means that many people in charge have surprisingly little experience with monitoring. Usually, some monitoring tool has been in use for years, every now and then an update is done, a few new devices are integrated into the monitoring setup, and that’s it. Surprisingly often, there is no central monitoring solution at all, and systems are only monitored with on-board tools. Only when massive failures and damage occur due to an unrecognized malfunction does the topic of monitoring move to the top of the agenda. A frantic evaluation of the monitoring market begins, at the end of which there is often a price that massively exceeds the actual budget.
This article provides clarity and prevents unpleasant surprises by describing the monitoring market, explaining licensing models, pointing out price traps, and giving concrete tips for the successful evaluation of a (new) monitoring solution.
Essentially, two types of monitoring tools are required for the day-to-day operation of a traditional IT environment: IT infrastructure monitoring tools (ITIM) and network performance monitoring and diagnostics tools (NPMD). Application performance monitoring (APM) tools also appear as a category but are primarily aimed at DevOps rather than ITOps or administrators, so we’ll leave those out of consideration here. Let’s look at the range of solutions for ITIM and NPMD. Here we find three different concepts:
Such tools provide in-depth analyses of specialized areas, as required by experts. Typical examples are, for example, NPMD tools that use flow protocols or packet sniffing to examine the data traffic in the network. Depending on their focus, they analyze security aspects, user experience and application performance, or the overall performance of the network. These tools are usually relatively expensive and require experts to use them successfully. In return, they provide a tremendous depth of data and can be valuable in determining the root cause of problems.
Plixer, Flowmon, or Wireshark are examples in the NPMD area; in the infrastructure area, there are numerous native solutions from manufacturers such as VMware or IBM that offer deep insights into their own systems – but only into these.
Such broad solutions pay special attention to easy implementation and operation. They monitor the entire infrastructure or network with all its components, including superficial traffic measurement, always focusing on a broad overview rather than deep analysis. These tools provide the foundation for the day-to-day operation of an IT environment; they are the multi-tool of the admin or a helpdesk team and run on the overview screen in the NOC. Ideally, they can be combined with specialist solutions: the broad solution takes care of the initial alerting and shows correlations to other areas, while the specialized solution enables more in-depth root cause analysis.
Solarwind‘s Network Performance Monitor or ManageEngine OpManager are examples of broad NPMD solutions, while Checkmk or Nagios offer a comprehensive feature set in the infrastructure area. Paessler PRTG offers an even broader feature set in one software by including both infrastructure and network.
Examples of broad suites include Solarwinds and ManageEngine. Some vendors offer comprehensive suites consisting of a wide variety of tools, modules, and add-ons that provide both a broad overview and give specialists on the team the analyses they need. In most cases, these are bought-in solutions that are not really integrated with each other but merely displayed on a higher-level dashboard. Alternatively, some vendors of broad-based solutions offer interfaces to incorporate specialized tools and operate partner networks to support their customers with appropriate integrations.
First of all, make sure that you know what you need. An accurate inventory is elementary.
We have determined our needs and identified possible solutions. Before we embark on a detailed technical evaluation, we should take a look at licensing. Otherwise, we may spend a lot of time and effort identifying a solution as technically suitable, only to discover in the end that the price of the required licenses is completely beyond the available scope. The type of licensing does not make software cheap or expensive, but it can provide transparency or disguise the actual price. Some tools are licensed by the number of users, others by the number of monitoring servers, monitored devices, or aspects monitored on devices. There are subscription models that are billed monthly or annually and models that combine a one-time license purchase with ongoing maintenance costs. The subscription model incurs higher ongoing costs but avoids costly initial investment in the license (OpEx instead of CapEx). In some companies, this can facilitate the release. Solutions that are only available as a purchase option, on the other hand, keep follow-up costs manageable.
With regards to licensing, you should pay particular attention to the scope of functions. Essentially, we can distinguish between three models here:
September 30, 2023
September 29, 2023
September 27, 2023
September 20, 2023
September 13, 2023
September 11, 2023
September 08, 2023
Previous
Integrated monitoring is the most important AIOps feature
Next
Green coding: another contributor to IT sustainability