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

InfluxDB vs Loom Systems comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 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

InfluxDB
Ranking in IT Infrastructure Monitoring
21st
Average Rating
8.2
Reviews Sentiment
6.4
Number of Reviews
15
Ranking in other categories
Non-Relational Databases (2nd), Open Source Databases (8th), Network Monitoring Software (23rd), NoSQL Databases (6th)
Loom Systems
Ranking in IT Infrastructure Monitoring
60th
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (4th)
 

Mindshare comparison

As of January 2026, in the IT Infrastructure Monitoring category, the mindshare of InfluxDB is 0.5%, up from 0.5% compared to the previous year. The mindshare of Loom Systems is 0.6%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring Market Share Distribution
ProductMarket Share (%)
InfluxDB0.5%
Loom Systems0.6%
Other98.9%
IT Infrastructure Monitoring
 

Featured Reviews

HJ
Senior System Developer at Norled
Tracking vessel movements seamlessly with continuous data collection and query execution
We mainly write and read data from InfluxDB. We perform very simple queries to do time series on a key, which is a unique ID of the vessel. We will select a vessel and select from time to time stamp. That’s what we do. InfluxDB’s core functionality is crucial as it allows us to store our data and execute queries with excellent response times.
Keerthi Kumar Sangaraju - PeerSpot reviewer
Technology Manager at a tech services company with 10,001+ employees
Stable, easy to set up, flexible, and has multiple functionalities, but needs to define priority levels for each incident
What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority.

Quotes from Members

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

Pros

"My advice for others looking into using InfluxDB is to use it the same way I did, because it is really stable, easy and friendly to use, and it is a great product overall."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"In our case, it started with a necessity to fill the gap that we had in monitoring. We had very reactive monitoring without trend analysis and without some advanced features. We were able to implement them by using a time series database. We are able to have all the data from applications, logs, and systems, and we can use a simple query language to correlate all the data and make things happen, especially with monitoring. We could more proactively monitor our systems and our players' trends."
"While I would rate InfluxDB a ten on a scale of one to ten, users should be thoughtful about matching the engine to their specific needs."
"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."
"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."
"The solution is very powerful."
"The user interface is well-designed and easy to use. It provides a clear overview of the data, making it simple to understand the information at hand."
"You can develop your own apps within Loom, and they can be configured very simply."
"The solution is absolutely scalable. If an organization needs to expand it out they definitely can."
"The RFS portion of the solution is the product's most valuable feature."
"What I like best about Loom Systems is that you can use it for infrastructure monitoring. I also like that it's a flexible solution."
 

Cons

"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"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."
"InfluxDB can improve by including new metrics on other technologies. They had some changes recently to pool data from endpoints but the functionality is not good enough in the industry."
"The solution doesn't have much of a user interface."
"The solution's UI can be more user-friendly."
"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."
"The error logging capability can be improved because the logs are not very informative."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy,"
"The reporting is a bit weak. They should work to improve this aspect of the product."
"What's lacking in Loom Systems is the level of priority for each incident. For example, after implementation and there was a huge impact on the client, and the client comes back to you and says that there's an incident, that there needs to be an immediate resolution for it, you'll see severity one, severity two, etc., in Loom Systems, rather than priority levels. It would be better if the incidents can be defined as low priority, medium priority, or high priority."
"The change management within the solution needs to be improved. There needs to be more process automation."
 

Pricing and Cost Advice

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

Top Industries

By visitors reading reviews
Manufacturing Company
10%
Financial Services Firm
10%
Computer Software Company
9%
University
9%
No data available
 

Company Size

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

Questions from the Community

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...
Ask a question
Earn 20 points
 

Comparisons

 

Overview

 

Sample Customers

ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
Citrix, Amdocs, Sysaid, Hexaware, Effibar, Revtrak, Taptica
Find out what your peers are saying about InfluxDB vs. Loom Systems and other solutions. Updated: January 2026.
880,745 professionals have used our research since 2012.