[jira] [Comment Edited] (SOLR-11779) Basic long-term collection of aggregated metrics

["David Smiley (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-11779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16405471#comment-16405471 ] 

David Smiley edited comment on SOLR-11779 at 3/19/18 9:19 PM:
--------------------------------------------------------------

[~otis] Is there some standard/common API for Solr to query such an external system without depending on a particular implementation?  If not I suppose a few could be coded to some internal plugin API -- just one at first.  

To Otis's point, I think it's pretty reasonable to say that the "sophisticated" autoscaling strategies require the user to do more -- like install some thingamajig.  In doing so, we keep our code base simpler?


was (Author: dsmiley):
[~otis] Is there some standard/common API for Solr to query such an external system without depending on a particular implementation?  If not I suppose a few could be coded to some internal plugin API -- just one at first.  

To Oti's point, I think it's pretty reasonable to say that the "sophisticated" autoscaling strategies require the user to do more -- like install some thingamajig.  In doing so, we keep our code base simpler?

> 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
>
> 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