[
https://issues.apache.org/jira/browse/SOLR-11779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16406079#comment-16406079
]
Andrzej Bialecki commented on SOLR-11779:
------------------------------------------
I agree that complex metrics analytics is definitely something outside the
scope of core Solr, excellent external tools to do that already exist and I'm
not proposing that we add this functionality here.
Again, the goal is to have an out-of-the-box simple API for storing and
tracking some of the key metrics, with minimum impact on cluster resources, in
order to better understand the momentary and long-term cluster behavior and
using it in autoscaling strategies, as well as for the purpose of basic (with
the stress on "basic"!) diagnostics and admin UI presentation.
This would provide a good way for users to be able to report and discuss these
metrics without requiring any particular setup on their part, or exposing too
many details about their cluster - just take a screenshot of a graph in the
admin UI.
Chronix looks really cool, but its functionality is overkill for this goal, and
we don't actually need detailed historical data for this purpose so we're ok
with the loss of resolution over time.
Storing each data point as a separate SolrDocument is probably too wasteful and
it would also mean reimplementing all sampling and consolidation algorithms
that are needed for maintaining multi-resolution time-series, as well as simple
graphing, all of which are already implemented in RRD4j. Individual datapoints
or their ranges can be easily retrieved from RrdDb blobs and can be represented
as Solr docs as needed.
> 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: [email protected]
For additional commands, e-mail: [email protected]
