Return-Path: <issues-return-30378-archive-asf-public=cust-asf.ponee.io@ambari.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 54273200BC9
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Fri, 11 Nov 2016 21:37:01 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 52F31160AF6; Fri, 11 Nov 2016 20:37:01 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id A3868160B01
	for <archive-asf-public@cust-asf.ponee.io>; Fri, 11 Nov 2016 21:37:00 +0100 (CET)
Received: (qmail 72961 invoked by uid 500); 11 Nov 2016 20:36:59 -0000
Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@ambari.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@ambari.apache.org>
List-Post: <mailto:issues@ambari.apache.org>
List-Id: <issues.ambari.apache.org>
Reply-To: dev@ambari.apache.org
Delivered-To: mailing list issues@ambari.apache.org
Received: (qmail 72908 invoked by uid 99); 11 Nov 2016 20:36:59 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Nov 2016 20:36:59 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 9B9432C4C72
	for <issues@ambari.apache.org>; Fri, 11 Nov 2016 20:36:59 +0000 (UTC)
Date: Fri, 11 Nov 2016 20:36:59 +0000 (UTC)
From: "Tim Thorpe (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.13019831.1478783654000.257902.1478896619634@Atlassian.JIRA>
In-Reply-To: <JIRA.13019831.1478783654000@Atlassian.JIRA>
References: <JIRA.13019831.1478783654000@Atlassian.JIRA> <JIRA.13019831.1478783654336@arcas>
Subject: [jira] [Updated] (AMBARI-18846) Custom services should be able to
 easily specify their own dashboards
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Fri, 11 Nov 2016 20:37:01 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-18846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tim Thorpe updated AMBARI-18846:
--------------------------------
    Attachment: AMBARI-18846.patch

> Custom services should be able to easily specify their own dashboards
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-18846
>                 URL: https://issues.apache.org/jira/browse/AMBARI-18846
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-admin, ambari-metrics, ambari-server
>    Affects Versions: trunk, 2.4.0, 2.5.0
>            Reporter: Tim Thorpe
>            Assignee: Tim Thorpe
>             Fix For: trunk, 2.5.0
>
>         Attachments: AMBARI-18846.patch
>
>
>  Currently all dashboards are added directly in under the AMBARI_METRICS package directory (package/files/grafana-dashboards).
> In order for custom services to add dashboards, they need to add the files directly under that folder.  Each time the Ambari server is upgraded, those files will be lost as the AMBARI_METRICS service definition will be replaced.
> This JIRA proposes adding a new directory under the ambari-server/resources.  This will contain both the dashboards and metrics for custom services.  
> The dashboards here will not be organized by stack.  Each service will add a directory containing their dashboards and will add a metrics file.
> resources/dashboards/grafana-dashboards/MY_SERVICE/<dashboards>
> resources/dashboards/service-metrics/MY_SERVICE.txt
> The resources/dashboards directory will need to get sync'd to the agents.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)