InfluxDB vs. Virtana Platform

InfluxDB is very good at storing monitoring metrics (e.g. performance data). InfluxDB is not the right choice if you need to store other data types (like plain text, data relations etc.).

Incentivized

Overall I would say that we have been very happy with Zenoss. It has been a great server monitoring tool. There are certain aspects that we would like to expand into, such as Capacity Planning, Network Performance Monitoring, and log analysis. We have coupled Zenoss logs with Splunk for external log management, but would like to start using some of the built-in analysis tools.

• Perfect handling telemetry data.
• Low latency, near real time.
• SQL-like language makes it easier to query.

Incentivized

• Monitoring Windows, Unix/Linux, Infra apps, storage, virtualization, converge infra etc..
• Integrate with other monitoring tools and receive events for aggregation and correlation
• Integration with ITSM( SNOW) for auto ticket creation

Incentivized

• GUI based administrator console

Incentivized

• It can be tricky to set-up depending on what you want to do.
• They have their own proprietary way of visualizing metrics, which is clever but does have a slight learning curve.

Incentivized

InfluxDB is a near perfect product for time series database engines. The relatively small list of cons are heavily outweighed by it's ability to just work and be a very flexible and powerful database engine. The community and support provided by the corporation are the only areas I have little experience.

Incentivized

We have worked with the InfluxDB support team a few times so far and it has been positive. Issues submitted are worked on promptly and we have good feedback.

Incentivized

Anytime we've had issues they have been very responsive and professional.

Incentivized

To be honest, I didn't look at alternatives since InfluxDB performs very well if you can oversee the lack of security and HA features. But for all challenges, there is an easy solution which brings you forward (e.g. read load balancing can be achieved by using a common HTTPS load balancer).

Incentivized

We strongly prefer Metricly for AWS Cost Analysis -- whereas other tools are easier to use on a traditional monitoring basis. To be clear, Merticly's monitoring tools are GREAT, but they require tuning and manual setup that we didn't have the time for on a small Platform Operations team. We have worked closely with Metricly to expand on their cost analysis capabilities, and plan to use them going forward.

Incentivized

• Provided us a time series DB.
• With the SQL-like language, it is very easy to learn.
• Empowered us to keep track of our events.

Incentivized

• We're a reseller/Integrator, so this question has a somewhat different meaning to our business. For us, Zenoss Cloud allows us to provide a single Cloud-based monitoring platform that can address virtually all our clients' use cases, dramatically simplifying our training and staffing requirements. Instead of training Engineers on several platforms, including the installation of physical hardware/software, we can focus on a single platform.
• The faster time-to-deployment and always-on cloud platform is a great fit for DevOps environments and newer software-defined data center platforms. The ability of Zenoss to support these environments solves what has been a major blind spot, slowing adoption of platforms that have been difficult to effectively manage with legacy monitoring platforms.
• For clients, the ability to consolidate from multiple prem-based tools to a single cloud-based platform is huge. Eliminating multiple licenses and ongoing hardware & administration costs can show a 1-2 year ROI.