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
26th
Average Rating
8.2
Reviews Sentiment
6.6
Number of Reviews
11
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (9th), Network Monitoring Software (22nd), NoSQL Databases (4th)
Loom Systems
Ranking in IT Infrastructure Monitoring
63rd
Average Rating
8.0
Reviews Sentiment
6.9
Number of Reviews
4
Ranking in other categories
Anomaly Detection Tools (2nd)
 

Mindshare comparison

As of August 2025, in the IT Infrastructure Monitoring category, the mindshare of InfluxDB is 0.6%, up from 0.3% compared to the previous year. The mindshare of Loom Systems is 0.3%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
IT Infrastructure Monitoring
 

Featured Reviews

DeepakR - PeerSpot reviewer
An open-source database that can be used to insert data
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.
Keerthi Kumar Sangaraju - PeerSpot reviewer
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

"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."
"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."
"The platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana."
"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."
"The solution is very powerful."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"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."
"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. If an organization needs to expand it out they definitely can."
"The RFS portion of the solution is the product's most valuable feature."
 

Cons

"The solution doesn't have much of a user interface."
"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."
"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."
"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."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"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."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"The discovery and mapping still takes a lot of human intervention, it's quite resource heavy,"
"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."
"The reporting is a bit weak. They should work to improve this aspect of the product."
 

Pricing and Cost Advice

"InfluxDB is open-source, but there are additional costs for scaling."
"We are using the open-source version of InfluxDB."
"InfluxDB recently increased its price. It is very expensive now."
"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.
865,384 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
12%
Computer Software Company
11%
Comms Service Provider
8%
Manufacturing Company
8%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
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?
It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster. Replicating data for on-prem development and testing is difficult. Having a SQL abstrac...
What is your primary use case for InfluxDB?
InfluxDB is the main component in our large enterprise-scale streaming data application for maritime vessels. We collect position data from vessels around the coast once per second, put it on a Kaf...
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: July 2025.
865,384 professionals have used our research since 2012.