Return-Path: 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 78D42200C1C for ; Wed, 15 Feb 2017 11:29:50 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 779FA160B46; Wed, 15 Feb 2017 10:29:50 +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 C4701160B5E for ; Wed, 15 Feb 2017 11:29:49 +0100 (CET) Received: (qmail 70164 invoked by uid 500); 15 Feb 2017 10:29:49 -0000 Mailing-List: contact issues-help@eagle.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@eagle.apache.org Delivered-To: mailing list issues@eagle.apache.org Received: (qmail 70155 invoked by uid 99); 15 Feb 2017 10:29:48 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Feb 2017 10:29:48 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 8948EC144F for ; Wed, 15 Feb 2017 10:29:48 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 9-pqUulNvKoo for ; Wed, 15 Feb 2017 10:29:48 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D74B45F659 for ; Wed, 15 Feb 2017 10:29:47 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DEA76E07DA for ; Wed, 15 Feb 2017 10:29:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 33ED22413C for ; Wed, 15 Feb 2017 10:29:42 +0000 (UTC) Date: Wed, 15 Feb 2017 10:29:42 +0000 (UTC) From: "jianzhong.chen (JIRA)" To: issues@eagle.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (EAGLE-898) Show jmx dashboard background first, then render the chart as that in JPM application MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 15 Feb 2017 10:29:50 -0000 jianzhong.chen created EAGLE-898: ------------------------------------ Summary: Show jmx dashboard background first, then render the chart as that in JPM application Key: EAGLE-898 URL: https://issues.apache.org/jira/browse/EAGLE-898 Project: Eagle Issue Type: Improvement Components: App::Hadoop JMX Monitor Reporter: jianzhong.chen Assignee: Chang chen Priority: Minor While opening the metrics dashboard, we can experience an explicit latency to get those dashboard charts. If we can not quickly solve the latency issue recently, can we first show all the background of dashboard charts, then render the charts. -- This message was sent by Atlassian JIRA (v6.3.15#6346)