lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-11779) Basic long-term collection of aggregated metrics
Date Tue, 12 Jun 2018 08:29:00 GMT

    [ 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


Mime
View raw message