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 4578A200C79 for ; Thu, 4 May 2017 13:34:09 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 4448B160BB0; Thu, 4 May 2017 11:34:09 +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 9209A160B9F for ; Thu, 4 May 2017 13:34:08 +0200 (CEST) Received: (qmail 59702 invoked by uid 500); 4 May 2017 11:34:07 -0000 Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list dev@ignite.apache.org Received: (qmail 59691 invoked by uid 99); 4 May 2017 11:34:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 May 2017 11:34:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 5E8781A0401 for ; Thu, 4 May 2017 11:34:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id hu2V72GNlcQV for ; Thu, 4 May 2017 11:34:06 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 926915FB29 for ; Thu, 4 May 2017 11:34:05 +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 C08AFE0C0D for ; Thu, 4 May 2017 11:34:04 +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 3529A21DF1 for ; Thu, 4 May 2017 11:34:04 +0000 (UTC) Date: Thu, 4 May 2017 11:34:04 +0000 (UTC) From: "Ivan Veselovsky (JIRA)" To: dev@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (IGNITE-5168) Expose IGFS metrics via an MBean or console Visor. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 04 May 2017 11:34:09 -0000 Ivan Veselovsky created IGNITE-5168: --------------------------------------- Summary: Expose IGFS metrics via an MBean or console Visor. Key: IGNITE-5168 URL: https://issues.apache.org/jira/browse/IGNITE-5168 Project: Ignite Issue Type: New Feature Components: IGFS Affects Versions: 2.0 Reporter: Ivan Veselovsky Assignee: Ivan Veselovsky Now in Ignite the only way to see IGFS metrics is to get them programmically from the code. But customers need them to understand what is cached in IGFS, so to expose the metrics would be useful. There are options to expose the metrics via MBean and/or via console Visor interface. -- This message was sent by Atlassian JIRA (v6.3.15#6346)