We performed a comparison between Elastic Observability and Zenoss Cloud 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."The product has connectors to many services."
"The price is very less expensive compared to the other solutions."
"The solution has been stable in our usage."
"We can view and connect different sources to the dashboard using it."
"Its diverse set of features available on the cloud is of significant importance."
"The solution is open-source and helps with back-end logging. It is also easy to handle."
"We use AppDynamics and Elastic. The reason why we're using Elastic APM is because of the license count. It's very favorable compared to AppDynamics. It's inexpensive; it's economical."
"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."
"Its Docker Container concept is mind blowing. It is the first monitoring tool which comes with Docker features."
"The custom built integration is one of the most valuable features because you can see all the especially critical items."
"It's easy to use."
"They have also accommodated many state-of-the-art technologies like Docker and ZooKeeper."
"What I like most about Zenoss Service Dynamics is that it monitors the devices and gives close to real-time alerts. For example, in case the device is not available, Zenoss Service Dynamics generates an alert so my team can resolve the issue."
"The product offers good documentation that helps with initial training."
"The most valuable feature is the flexible discovery mechanism."
"Elastic Observability is reactive rather than proactive. It should act as an ITSM tool and be able to create tickets and alerts on Jira."
"The price is the only issue in the solution. It can be made better and cheaper."
"The auto-discovery isn't nearly as good. That's a big portion of it. When you drop the agent onto the JVM and you're trying to figure things out, having to go through and manually do all that is cumbersome."
"Elastic Observability needs to have better standardization, logging, and schema."
"There could be more low-code features included in the product."
"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."
"Improving code insight related to infrastructure and network, particularly focusing on aspects such as firewalls, switches, routers, and testing would be beneficial."
"The tool's scalability involves a more complex implementation process. It requires careful calculations to determine the number of nodes needed, the specifications of each node, and the configuration of hot, warm, and cold zones for data storage. Additionally, managing log retention policies adds further complexity. The solution's pricing also needs to be cheaper."
"As Zenoss Service Dynamics is more for network-centric devices and you want to monitor, for example, a server, its services, IP addresses, and interfaces, if it's a network and you're going to monitor multiple items, you'll be charged multiple times. This is what Zenoss Service Dynamics needs to improve to make sure that customers pay just one fee to monitor the entire server. What I'd like to see in Zenoss Service Dynamics in the future is a public cloud monitoring feature, particularly for the Azure public cloud. Another additional feature I'd like to see in the next release of the solution is integration with the Azure public cloud because I know that there are some services from Azure that Zenoss Service Dynamics is currently unable to monitor."
"There is room for improvement with the administrative part. They introduced Control Center to manage things in Zenoss 5. The services that Zenoss provides remained the same, but the administrative part, since they introduced Docker, etc., has become a little complex"
"It would be ideal if the product offered sound alerts."
"Now it is stable, but they should design threshold parameters in percentage instead of raw values."
"The AI aspect needs to improve."
"There was a problem with Zenoss and storage monitoring."
"The inclusion of a feature to show a graphical view of the network would be a helpful improvement."
Elastic Observability is ranked 10th in IT Infrastructure Monitoring with 22 reviews while Zenoss Cloud is ranked 47th in IT Infrastructure Monitoring with 8 reviews. Elastic Observability is rated 7.8, while Zenoss Cloud is rated 8.4. 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 Zenoss Cloud writes "Generates close to real-time alerts so users can resolve issues, but needs more integration and public cloud monitoring features". Elastic Observability is most compared with Dynatrace, New Relic, AppDynamics, Azure Monitor and Sentry, whereas Zenoss Cloud is most compared with Zabbix, Nagios XI, ServiceNow IT Operations Management, SCOM and ScienceLogic. See our Elastic Observability vs. Zenoss Cloud report.
See our list of best IT Infrastructure Monitoring vendors, best Container Monitoring vendors, and best Cloud Monitoring Software 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.