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

InfluxDB vs Loom Systems comparison

Why PeerSpot?
 

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 (16th), NoSQL Databases (7th)
Loom Systems
Ranking in IT Infrastructure Monitoring
69th
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (5th)
 

Mindshare comparison

As of November 2026, in the IT Infrastructure Monitoring category, the mindshare of InfluxDB is 0.8%, up from 0.5% compared to the previous year. The mindshare of Loom Systems is 0.5%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring Mindshare Distribution
ProductMindshare (%)
InfluxDB0.8%
Loom Systems0.5%
Other98.7%
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 most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"Based on InfluxDB, we have great analytics produced by our SRE team, and with that, we have an alerting and monitoring system in place."
"The solution is very powerful."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"I recommend going with the cloud version of InfluxDB, as it's very cheap and effective."
"InfluxDB has positively impacted Energy Box by being the best choice for our needs."
"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."
"This product has been working well and it is serving our purpose, so I can recommend it to others."
"The RFS portion of the solution is the product's most valuable feature."
"Bringing Loom in ensures that the incident process, request process, change, all of these processes are improved."
"The solution is absolutely scalable. If an organization needs to expand it out they definitely can."
"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."
"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."
"You can develop your own apps within Loom, and they can be configured very simply."
"The solution is absolutely scalable."
 

Cons

"The interface of InfluxDB is so complex and should be made easier for non-technical people."
"The solution doesn't have much of a user interface."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"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."
"However, I cannot ignore the challenges I faced while configuring the database with my message brokers, whether Rabbit or Kafka, because the documentation is not properly provided."
"InfluxDB can be improved by addressing issues such as performance drops, queries being more difficult to understand, and its high memory usage."
"However, I do wish the documentation and community resources around Flux were more extensive and beginner-friendly."
"The error logging capability can be improved because the logs are not very informative."
"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 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."
"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."
"The reporting is a bit weak. They should work to improve this aspect of the product."
 

Pricing and Cost Advice

"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.
920,929 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
12%
Manufacturing Company
10%
Financial Services Firm
10%
Outsourcing Company
10%
Construction Company
23%
Financial Services Firm
13%
Comms Service Provider
6%
Healthcare Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise5
Large Enterprise9
No data available
 

Questions from the Community

What needs improvement with InfluxDB?
If the dashboarding facility can be improved in terms of the visualization parameters and the amount of support available from the community, as well as having smarter alerts to send those alerts t...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is to inject all my performance data and visualize it as a data source into Grafana. My data comes from JMeter from a plugin, which is inserting data to InfluxDB, and ...
What advice do you have for others considering InfluxDB?
It is good to start with InfluxDB to stabilize your data, visualize your data, and have the data stored on a time-series basis. I would recommend everyone to get into InfluxDB and start using it. T...
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: November 2026.
920,929 professionals have used our research since 2012.