You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hari Sekhon (JIRA)" <ji...@apache.org> on 2018/07/17 11:17:00 UTC
[jira] [Updated] (AMBARI-24295) Integrate OpenTSDB + replace Ambari
Metrics Collector
[ https://issues.apache.org/jira/browse/AMBARI-24295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hari Sekhon updated AMBARI-24295:
---------------------------------
Summary: Integrate OpenTSDB + replace Ambari Metrics Collector (was: Integrate OpenTSDB to replace Ambari Metrics Collector)
> Integrate OpenTSDB + replace Ambari Metrics Collector
> -----------------------------------------------------
>
> Key: AMBARI-24295
> URL: https://issues.apache.org/jira/browse/AMBARI-24295
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-metrics
> Affects Versions: 2.5.2
> Environment: HDP 2.6
> Reporter: Hari Sekhon
> Priority: Major
>
> Request to integrate OpenTSDB for metrics collection and replace the Ambari Metrics Collector with OpenTSDB.
> OpenTSDB is a much more widely used, tested and scaled metrics time series database.
> It is run by Hortonworks clients for doing real world metrics collection without worrying about retention.
> Both AMS and OpenTSDB already run on HBase, so only AMS Collector needs to be swapped out.
> Standard Grafana as you find in companies doesn't have the data source to query Ambari AMS but can query OpenTSDB natively, so this is more compatible with the outside monitoring ecosystem.
> Ambari should be able to scale this easily just by adding RegionServers and TSD instances.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)