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."I have built a mini business intelligence system based on Elastic Observability."
"It has always been a stable solution."
"It's easy to deploy, and it's very flexible."
"It is a powerful tool that allows users to collect and transform logs as needed, enabling flexible visualization and analysis."
"Good design and easy to use once implemented."
"We can view and connect different sources to the dashboard using it."
"Elastic Observability significantly improves incident response time by providing quick access to logs and data across various sources. For instance, searching for specific keywords in logs spanning over a month from multiple data sources can be completed within seconds."
"Elastic APM has plenty of features, such as the Elastic server for Kibana and many additional plugins. It's a comprehensive tool when used as a logging platform."
"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."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"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 most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"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 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 features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"The solution is very powerful."
"There is room for improvement regarding its APM capabilities."
"Improving code insight related to infrastructure and network, particularly focusing on aspects such as firewalls, switches, routers, and testing would be beneficial."
"Elastic Observability is reactive rather than proactive. It should act as an ITSM tool and be able to create tickets and alerts on Jira."
"In the future, Elastic APM needs a portfolio iTool. They can provide an easy way to develop the custom UI for Kibana."
"The interface could be improved."
"The price is the only issue in the solution. It can be made better and cheaper."
"Elastic APM's visualization is not that great compared to other tools. It's number of metrics is very low."
"The cost must be made more transparent."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"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 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."
"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 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."
Elastic Observability is ranked 10th in IT Infrastructure Monitoring with 22 reviews while InfluxDB is ranked 36th 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.