We performed a comparison between Elastic Observability and InfluxDB based on real PeerSpot user reviews.
Find out in this report how the two IT Infrastructure Monitoring solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It's easy to deploy, and it's very flexible."
"The Elastic User Interface framework lets us do custom development when needed. You need to have some Javascript knowledge. We need that knowledge to develop new custom tests."
"For full stack observability, Elastic is the best tool compared with any other tool ."
"The solution allows us to dig deep into data."
"Its diverse set of features available on the cloud is of significant importance."
"It has always been a stable solution."
"The solution is open-source and helps with back-end logging. It is also easy to handle."
"The price is very less expensive compared to the other solutions."
"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."
"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'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."
"The solution is very powerful."
"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."
"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"More web features could be added to the product."
"Elastic Observability needs to improve the retrieval of logs and metrics from all the instances."
"There's a steep learning curve if you've never used this solution before."
"The cost must be made more transparent."
"Elastic Observability is difficult to use. There are only three options for customization but this can be difficult for our use case. We do not have other options to choose the metrics shown, such as CPU or memory usage."
"Elastic Observability is reactive rather than proactive. It should act as an ITSM tool and be able to create tickets and alerts on Jira."
"Elastic Observability’s price could be improved."
"Elastic Observability needs to have better standardization, logging, and schema."
"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."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"The error logging capability can be improved because the logs are not very informative."
"The solution's UI can be more user-friendly."
"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."
"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."
Elastic Observability is ranked 10th in IT Infrastructure Monitoring with 22 reviews while InfluxDB is ranked 37th in IT Infrastructure Monitoring with 8 reviews. Elastic Observability is rated 7.8, while InfluxDB is rated 7.6. The top reviewer of Elastic Observability writes "The user interface framework lets us do custom development when needed. ". On the other hand, the top reviewer of InfluxDB writes "A powerful, lightweight time series database with a simple query language and easy setup". Elastic Observability is most compared with Dynatrace, New Relic, AppDynamics, Azure Monitor and Sentry, whereas InfluxDB is most compared with MongoDB, Cassandra, Netdata, ScyllaDB and Cloudera Distribution for Hadoop. See our Elastic Observability vs. InfluxDB report.
See our list of best IT Infrastructure Monitoring vendors.
We monitor all IT Infrastructure Monitoring reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.