Prometheus与ElasticSearch.哪个对容器和服务器监视更好? [英] Prometheus vs ElasticSearch. Which is better for container and server monitoring?

问题描述

ElasticSearch是一个文档存储，更是一个搜索引擎，我认为ElasticSearch并不是监视高维数据的好选择，因为它消耗大量资源.另一方面，普罗米修斯(Prometheus)是TSDB，用于捕获高维数据.

ElasticSearch is a document store and more of a search engine, I think ElasticSearch is not good choice for monitoring high dimensional data as it consumes lot of resources. On the other hand prometheus is a TSDB which is designed for capturing high dimensional data.

任何对此有经验的人，请告诉我什么是与容器和服务器监视一起使用的最佳工具.

Anyone experienced in this please let me know what's the best tool to go with for container and server monitoring.

推荐答案

ELK是通用的非SQL堆栈，可以使用 进行监视.我们已经成功地在生产环境中部署了一个，并将其用于我们的监控系统的某些方面.您可以将指标引入其中(如果需要)，并使用它来监视它们，但是它并不是专门为实现此目的而设计的.非商业版本(7.9版)也没有附带警报系统-您需要为此设置另一个组件(例如Sensu)或支付ES商业许可证.

ELK is a general-purpose no-sql stack that can be used for monitoring. We've successfully deployed one on production and used it for some aspects of our monitoring system. You can ship metrics into it (if you wish) and use it to monitor them, but its not specifically designed to do that. Nor does the non-commercial version (version 7.9) come with an alerting system - you'll need to setup another component for that (like Sensu) or pay for ES commercial license.

普罗米修斯被设计用于监视.以及其度量标准收集客户端(或其他第三方客户端，例如 Telegraf 及其服务发现选项(例如领事)及其警报管理器正是完成这项工作的正确工具.

Prometheus, on the other hand, is designed to be used for monitoring. And along with its metric-gathering clients (or other 3rd party clients like Telegraf and its service discovery options (like consul) and its alert-manager is just the right tool for this job.

最终，这两种解决方案都可以使用，但是我认为Elasticsearch将需要更多的工作和更多的维护(我们发现ES集群很难维护-但这取决于您拥有的数据量).

Ultimately, both solutions can work, but in my opinion Elasticsearch will require more work and more upkeep (we found that ES clusters are a pain to maintain - but that depends on the amount of data you'll have).

这篇关于Prometheus与ElasticSearch.哪个对容器和服务器监视更好?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！