No more typing reviews! Try our Samantha, our new voice AI agent.

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
14th
Average Rating
8.0
Reviews Sentiment
6.5
Number of Reviews
20
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), Network Monitoring Software (13th), NoSQL Databases (6th)
Loom Systems
Ranking in IT Infrastructure Monitoring
64th
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (5th)
 

Mindshare comparison

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

Featured Reviews

Mugeesh Husain - PeerSpot reviewer
Team Lead, Software at Energybox
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.
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

"The platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana."
"I recommend going with the cloud version of InfluxDB, as it's very cheap and effective."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"This product has been working well and it is serving our purpose, so I can recommend it to others."
"The solution is very powerful."
"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."
"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."
"The solution is very powerful."
"The solution is absolutely scalable."
"The solution is very scalable; a company wouldn't have any issues expanding it if they needed to, and we have a few thousand users on the solution."
"The RFS portion of the solution is the product's most valuable feature."
"You can develop your own apps within Loom, and they can be configured very simply."
"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."
"The solution is absolutely scalable. If an organization needs to expand it out they definitely can."
"Bringing Loom in ensures that the incident process, request process, change, all of these processes are improved."
"What I like best about Loom Systems is that you can use it for infrastructure monitoring and that it's a flexible solution."
 

Cons

"InfluxDB can be improved in several ways. The Flux query language needs to be learned, but if there were something similar to SQL or previous options, it would be much easier for users without imposing a learning curve."
"The solution's UI can be more user-friendly."
"However, I do wish the documentation and community resources around Flux were more extensive and beginner-friendly."
"In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version."
"In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version."
"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."
"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."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"What's lacking in Loom Systems is the level of priority for each incident."
"The reporting is a bit weak."
"The change management within the solution needs to be improved. There needs to be more process automation."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy,"
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy, especially in the initial setup which can take six months of work, especially when you have a large estate that you're dealing with."
"The reporting is a bit weak. They should work to improve this aspect of the product."
"The change management within the solution needs to be improved. There needs to be more process automation."
"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."
 

Pricing and Cost Advice

"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."
"The tool is an open-source product."
Information not available
report
Use our free recommendation engine to learn which IT Infrastructure Monitoring solutions are best for your needs.
894,738 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Comms Service Provider
10%
Manufacturing Company
10%
University
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise4
Large Enterprise8
No data available
 

Questions from the Community

What needs improvement with InfluxDB?
InfluxDB can be improved by addressing issues such as performance drops, queries being more difficult to understand, and its high memory usage. InfluxDB is not suitable for relational databases lik...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is storing a time series database and analyzing data changes over time. I use InfluxDB to store my infrastructure and application metrics, logs, events, and data, and ...
What advice do you have for others considering InfluxDB?
I would advise others looking into using InfluxDB that if they want to store a time series database for monitoring, logging, and event-based tasks, and also want long-term retention of the database...
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: April 2026.
894,738 professionals have used our research since 2012.