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

InfluxDB vs Statseeker 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

InfluxDB
Ranking in Network Monitoring Software
52nd
Average Rating
8.2
Reviews Sentiment
6.5
Number of Reviews
10
Ranking in other categories
Non-Relational Databases (3rd), Open Source Databases (12th), IT Infrastructure Monitoring (45th), NoSQL Databases (5th)
Statseeker
Ranking in Network Monitoring Software
60th
Average Rating
8.2
Reviews Sentiment
7.6
Number of Reviews
38
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of May 2025, in the Network Monitoring Software category, the mindshare of InfluxDB is 0.3%, up from 0.3% compared to the previous year. The mindshare of Statseeker is 0.2%, down from 0.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software
 

Featured Reviews

PedroCampos - PeerSpot reviewer
A powerful, lightweight time series database with a simple query language and easy setup
Influx has TICK Stack, which contains multiple services and multiple products that work together. InfluxDB is just a time series database, and it works really well. I haven't yet had the time to look into the new stack based on Influx 2.0, but currently, as a time series database, InfluxDB is working the way it is supposed to work. 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 would also like to have high availability features, such as replication, active-active, etc. If they can put an extra plugin or service on top of it, it would be something interesting. I am not sure if they have high availability to make it data center-aware for clustering. For example, I am not sure whether you can have it at different locations with big clusters that are location-aware. Even in their documentation or presentation, they talk too little about high availability and extended clusters with different locations. They might already have it in the newer versions. We have Influx 1.8 in our production in the stage and internal workloads environments. The other products in their ecosystem, such as Chronograf, can be improved. Chronograf is a dashboarding or visualization layer product, and that, for sure, can be improved.
JH
Simplifies monitoring and provides real-time alerts for issues we might not immediately be aware of otherwise
The product has improved our organization by simplifying monitoring and giving real-time alerts for issues we might not immediately be aware of otherwise. If we notice five devices with latency or errors, I wouldn't know that if I didn't command line into 800 devices and check every day. I can see the status on the dashboard and it just makes it easy to know where the problems are. If we didn't have that capability by using Statseeker, then it would be very complex to monitor. We'd need to have another tool or manually log into every device to try to check things. And this product just does it all for us. That streamlines and improves our workload so that we only need to have two people in our office for the network team. It improves availability. If a circuit goes down texts and email alerts get sent out. So, even if it's in the evening or we're not on premises, we'll know if something's down. We use it all the time because it really helps.

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 feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"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."
"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."
"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."
"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."
"Being able to look back historically at the uptime and downtime is invaluable."
"It is fairly simple and easy to use as an all-purpose network monitor."
"In terms of network visibility, Statseeker can be very granular. We can tell it exactly where we want it to go and where we want it to check, or it can do an SNMP walk and find out where everything is. It's very detailed."
"We are now able to easily track where problems are with bandwidth and port errors, rather than having to do a lot of diagnostics."
"If somebody is complaining about slow networking then this solution allows us to see various ports to find out whether they are being overloaded."
"This solution allowed us to track down trouble users."
"The most important feature is just the fact that it doesn't aggregate the information up, and I can look at detailed information going back quite a long time."
"Grouping, Threshold/alerts, Netflow analyser, Private MIB object support are most valuable as they can provide more visibility into network performance, and for network troubleshooting."
 

Cons

"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"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 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's UI can be more user-friendly."
"The solution doesn't have much of a user interface."
"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 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."
"That user interface for selecting things needs to be a little more intuitive."
"It would be nice if they had twenty-four-hour technical support because we contact Australia and we have to wait for them to open."
"The interface could be more user-friendly and it would be nice if there were enhanced options for reporting."
"The inclusion of configuration management features and SIP links would improve this solution."
"I would like to have soft alarming. If an inner-base all of a sudden triggers a threshold, we have to rely on a lot of other tools and then we go into Statseeker to verify it. If Statseeker would confirm it preemptively and trigger it into our network panel, that would be nice."
"I'd say the interface could improve a little bit. I find with new users, I tend to have to spend a bit of time walking them through how to use the interface. It could be a little more user friendly."
"I would like to see fully automatic updates so that our version is always current."
"It would be very nice to have the Cisco ACI option included in the regular license."
 

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."
"InfluxDB recently increased its price. It is very expensive now."
"One thing that needs improvement is how it's licensed. I understand historically the company licensed it off a same charge for everyone. I understand the company needs to make money, but how they introduced the tiered licensing model, and then multiple layers of licensing was a bit of an issue. So, on the whole, coming up with a licensing model that isn't confusing and complicated and is easy to understand would be one way to improve the product. They have told me lately that they're changing how they license stuff, but they haven't made that - as I understand it - in their marketing material public knowledge as of yet. I would say that at the moment it's a bit convoluted. It's confusing. Some of their basic licensing model is a bit of a ripoff. If you go over five or ten support calls in the basic licensing model they start charging you for support calls. I think that's a bit rich."
"This tool would probably be priced well if it had deeper NetFlow capabilities, but for our use case, in particular, we're only recovering ports after ninety days and looking at circuit congestion, it's pretty pricey."
"We pay a yearly maintenance fee of approximately $40,000 USD."
"The yearly cost varies as per the number of devices being monitored. The cost for 25,000 devices is about $4500."
"When it came to selecting this solution, it came down to cost."
"We have permanent licenses so there's really no cost, other than ongoing maintenance. When I think about it, that's running us about $20,000 a year."
"We now feel the pricing is a good value. Previously we had a just a normal license but now we've got an Enterprise license. Since the Enterprise, it's been a lot better value. We did think it was pretty expensive before, but with the Enterprise license it's almost less than half that price. If you have a number of accounts within the organization that use Statseeker, I would suggest get the Enterprise license."
"Compared to other solutions such as Zabbix and AKiPS, this solution is very well priced."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
850,747 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
15%
Computer Software Company
13%
Manufacturing Company
9%
Comms Service Provider
7%
Financial Services Firm
19%
Computer Software Company
8%
University
8%
Energy/Utilities Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
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 coll...
What is your primary use case for InfluxDB?
I use the solution to store and manage data from various sensors in a production environment. I have developed a system where data from these sensors is communicated through an OPC UA receiver and ...
What is your experience regarding pricing and costs for Statseeker?
We are content with our current setup and its features. Additionally, we appreciate Statseeker's responsiveness to our queries and requests for improvements, particularly in monitoring. The upcomin...
What needs improvement with Statseeker?
There is a need for many developments to mature Statseeker. It should provide a study use case to show how it monitors the SD-WAN service.
What is your primary use case for Statseeker?
Statseeker provides the basic monitoring status of our network elements, including latency, ping delays, and ping drops. Its strengths lie in a couple of areas. Firstly, it is not an expensive tool...
 

Comparisons

 

Overview

 

Sample Customers

ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
With active deployments in over 22 countries and many Fortune 100 firms, Statseeker monitors millions of interfaces in real-time. Some example customers include: FedEx, Optus, Verizon, California State University, Department of Agriculture and Fisheries, Monash University, Texas A&M University.
Find out what your peers are saying about InfluxDB vs. Statseeker and other solutions. Updated: April 2025.
850,747 professionals have used our research since 2012.