From dev-return-325179-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Tue Jun 12 10:29:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 70555180608 for ; Tue, 12 Jun 2018 10:29:04 +0200 (CEST) Received: (qmail 87461 invoked by uid 500); 12 Jun 2018 08:29:03 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 87448 invoked by uid 99); 12 Jun 2018 08:29:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jun 2018 08:29:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 81BE6180821 for ; Tue, 12 Jun 2018 08:29:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 0KsIGWuZYldA for ; Tue, 12 Jun 2018 08:29:01 +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 62ED75F57E for ; Tue, 12 Jun 2018 08:29:01 +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 8017EE066E for ; Tue, 12 Jun 2018 08:29:00 +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 29A9420EAB for ; Tue, 12 Jun 2018 08:29:00 +0000 (UTC) Date: Tue, 12 Jun 2018 08:29:00 +0000 (UTC) From: "Andrzej Bialecki (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SOLR-11779) Basic long-term collection of aggregated metrics MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-11779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509333#comment-16509333 ] Andrzej Bialecki commented on SOLR-11779: ------------------------------------------ [~yseeley@gmail.com] this is relatively harmless, it simply means that while {{.system}} is absent the metrics history will be maintained in memory. We can probably skip logging the full stack trace. > Basic long-term collection of aggregated metrics > ------------------------------------------------ > > Key: SOLR-11779 > URL: https://issues.apache.org/jira/browse/SOLR-11779 > Project: Solr > Issue Type: New Feature > Security Level: Public(Default Security Level. Issues are Public) > Components: metrics > Affects Versions: 7.3, master (8.0) > Reporter: Andrzej Bialecki > Assignee: Andrzej Bialecki > Priority: Major > Fix For: 7.4, master (8.0) > > Attachments: SOLR-11779.patch, SOLR-11779.patch, SOLR-11779.patch, SOLR-11779.patch, c1.png, c2.png, core.json, d1.png, d2.png, d3.png, jvm-list.json, jvm-string.json, jvm.json, o1.png, u1.png > > > Tracking the key metrics over time is very helpful in understanding the cluster and user behavior. > Currently even basic metrics tracking requires setting up an external system and either polling {{/admin/metrics}} or using {{SolrMetricReporter}}-s. The advantage of this setup is that these external tools usually provide a lot of sophisticated functionality. The downside is that they don't ship out of the box with Solr and require additional admin effort to set up. > Solr could collect some of the key metrics and keep their historical values in a round-robin database (eg. using RRD4j) to keep the size of the historic data constant (eg. ~64kB per metric), but at the same providing out of the box useful insights into the basic system behavior over time. This data could be persisted to the {{.system}} collection as blobs, and it could be also presented in the Admin UI as graphs. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org