Try our new research platform with insights from 80,000+ expert users

Fortra's Intermapper vs InfluxDB comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 10, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Fortra's Intermapper
Ranking in Network Monitoring Software
84th
Average Rating
8.2
Number of Reviews
4
Ranking in other categories
No ranking in other categories
InfluxDB
Ranking in Network Monitoring Software
23rd
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
17
Ranking in other categories
Non-Relational Databases (2nd), Open Source Databases (8th), IT Infrastructure Monitoring (21st), NoSQL Databases (6th)
 

Mindshare comparison

As of January 2026, in the Network Monitoring Software category, the mindshare of Fortra's Intermapper is 0.4%, up from 0.2% compared to the previous year. The mindshare of InfluxDB is 0.3%, down from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software Market Share Distribution
ProductMarket Share (%)
InfluxDB0.3%
Fortra's Intermapper0.4%
Other99.3%
Network Monitoring Software
 

Featured Reviews

AL
SVP of Networking and Operations at Skywire Networks
It tremendously cuts down our troubleshooting timeframe, but needs advanced SLA monitoring and reporting
They can do a better job with SLA reporting. It does some basic reporting, but it really doesn't offer the ability to monitor devices by groups, customers, or carrier to give an overall health performance of specifically-defined environments. That's where HelpSystems Intermapper could have done a better job. I would love to see advanced SLA monitoring and reporting in this solution. They already have a lot of ingredients. They already have SNMP polling. It is really about what people are looking for from SLA monitoring, especially someone who looks at the network topology. You want to see your endpoints. You want to see half of your endpoints by simply analyzing ICMP or SNMP-based availability of your endpoints. Having an ability to define your group and how you bring devices into your group would be a huge benefit.
Mugeesh Husain - PeerSpot reviewer
Team Lead, Software at a tech vendor with 51-200 employees
Time series data has been managed efficiently for IoT sensors but reporting still needs improvement
How InfluxDB can be improved is relevant since for Energy Box, we face certain issues. We have customers worldwide, including the United States, United Kingdom, and Europe, but when we expanded to China two years ago, they indicated that they do not support the cloud version there. Our application is built on the cloud, which required us to create a separate application for Azure China, which was painful for us. The second issue involves frequent version changes. For example, we started with version one, transitioned to version two, and I heard they are considering InfluxDB version three, reverting to earlier practices. InfluxDB should improve without completely changing its approach. Now we have to redo our work for InfluxDB version three. Regarding needed improvements, the documentation is sufficient, but pricing presents a challenge. InfluxDB has standard pricing, which is acceptable for large companies. However, for startups in our position, they should provide special discounts so everyone can utilize it. The pricing should adapt as companies grow, which is a reasonable expectation.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"What is really cool about HelpSystems InterMapper is that because of its SNMP base, you can integrate all different makes and models on the same map. You, of course, can have more than one map, but you have an option to have visibility into the entire network from one centralized system. You can monitor IPs, routers, radios, DC power plants, and UPS. You can do it all from one network management and monitoring solution. That's what really makes HelpSystems Intermapper great. Another great thing about HelpSystems InterMapper is that you can really bundle different probes under one device. You can have a bundled device. You can monitor the physical status of a host based on the IP availability. You can also monitor services and actually see if anything happens. You can quickly determine whether it is the application layer, host layer, or network layer. HelpSystems Intermapper gives such a unique representation of a network. Ever since we started using HelpSystems InterMapper, we don't have to document everything in a detailed format and store it somewhere. Right now, it is really a combination of network topology, network monitoring, and network analyzing. So, in my opinion, it is awesome. When you have your SNMP topology defined, you don't require a dedicated NMS engineer to manage your system, which is another great thing about HelpSystems InterMapper. I see how our operators get so excited by having the ability to map a device or interface and connect interfaces together. HelpSystems InterMapper is also very operator friendly; not just user friendly, but also operator friendly. This is a unique feature, and it works really great."
"The most valuable features are its: log history, real-time monitoring capabilities, accuracy - the number of false positives is very low, and the mapping features."
"It's a nice graphical interface, a nice map, that relates Layer 1 to Layer 3, virtually instantly, to the Helpdesk support staff. It provides a default place to get critical information so we can deploy our staff."
"It's all today portal-based which is a good feature for us."
"The platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana."
"Overall, InfluxDB delivered excellent performance, stability, and simplicity for telemetry-driven use cases."
"InfluxDB reduced my time to show data without any interruption, also reducing the number of people needed to manage the project; it is very good to have InfluxDB in my project."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"InfluxDB's best feature is that it's a cloud offering. Other good features include its time-series DB, fast time-bulk queries, and window operations."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"InfluxDB is a database where you can insert data. However, it would be best if you had different components for alerting, data sending, and visualization. You need to install tools to collect data from servers. It must be installed on Windows or Linux servers. During installation, ensure that the configuration file is correct to prevent issues. Once data is collected, it can be sent to InfluxDB. For visualization, you can use open-source tools like Grafana."
"Based on InfluxDB, we have great analytics produced by our SRE team, and with that, we have an alerting and monitoring system in place."
 

Cons

"It's a smaller solution so tools are not as advanced as you would find in a larger solution"
"I'd love to see more of the network management side of it coming back into it. If we were able to run scripts to bounce ports on switches, that would be great. It's asking a lot, but it's actually very doable because I do it through scripting into other products. If we could incorporate that directly into Intermapper, that would be fantastic."
"They can do a better job with SLA reporting. It does some basic reporting, but it really doesn't offer the ability to monitor devices by groups, customers, or carrier to give an overall health performance of specifically-defined environments. That's where HelpSystems Intermapper could have done a better job. I would love to see advanced SLA monitoring and reporting in this solution. They already have a lot of ingredients. They already have SNMP polling. It is really about what people are looking for from SLA monitoring, especially someone who looks at the network topology. You want to see your endpoints. You want to see half of your endpoints by simply analyzing ICMP or SNMP-based availability of your endpoints. Having an ability to define your group and how you bring devices into your group would be a huge benefit."
"InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data collection for all KPIs. This happens because the agent stops working if there's an issue with any configuration part. To address this, it is essential to ensure that all configurations are part of the agent's EXE file when provided. This makes it easier to package the agent for server installation and ensures all KPIs are available from the server. Additionally, the agent cannot encrypt and decrypt passwords for authentication, which can be problematic when monitoring URLs or requiring authentication tokens. This requires additional scripting and can prolong service restart times."
"The solution doesn't have much of a user interface."
"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"The solution's UI can be more user-friendly."
"The error logging capability can be improved because the logs are not very informative."
"Sometimes, when we write too much data within a minute, the data count becomes excessive, reaching perhaps 100,000 or 500,000 data points, and InfluxDB gives a timeout exception, which we must handle in our application."
"The interface of InfluxDB is so complex and should be made easier for non-technical people."
"InfluxDB cannot be used for high-cardinality data. It's also difficult and time-consuming to write queries, and there are some issues with bulk API."
 

Pricing and Cost Advice

Information not available
"The tool is an open-source product."
"InfluxDB recently increased its price. It is very expensive now."
"We are using the open-source version of InfluxDB."
"InfluxDB is open-source, but there are additional costs for scaling."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
881,176 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Government
18%
Manufacturing Company
18%
Recreational Facilities/Services Company
8%
University
8%
Manufacturing Company
10%
Financial Services Firm
9%
Computer Software Company
9%
University
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business6
Midsize Enterprise3
Large Enterprise8
 

Questions from the Community

Ask a question
Earn 20 points
What do you like most about InfluxDB?
InfluxDB is a database where you can insert data. However, it would be best if you had different components for alerting, data sending, and visualization. You need to install tools to collect data ...
What needs improvement with InfluxDB?
Although I didn't encounter any significant challenges, I think that if there was a NoSQL version of InfluxDB, that would also help because I have used the SQL version. I wish InfluxDB were also av...
What is your primary use case for InfluxDB?
My main use case for InfluxDB involved working on a LEO satellite KPI monitoring application, where I gathered latency, throughput, packet loss, jitter, and various types of network data for severa...
 

Also Known As

HelpSystems Intermapper
No data available
 

Overview

 

Sample Customers

Greater Media Detroit, University of British Columbia, Don's Farm Supply
ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
Find out what your peers are saying about Fortra's Intermapper vs. InfluxDB and other solutions. Updated: December 2025.
881,176 professionals have used our research since 2012.