[
https://issues.apache.org/jira/browse/SOLR-11779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484495#comment-16484495
]
Andrzej Bialecki commented on SOLR-11779:
------------------------------------------
Updated patch:
* Overseer leader node now collects aggregated metrics from all nodes.
Aggregation method is just addition for now, which makes sense with the default
metrics that this patch collects. There's one history DB per each collection,
and one for {{solr.jvm}} and {{solr.node}} representing sort of global view of
the cluster.
* added support for configuration via {{solr.xml:/solr/metrics/history}} or via
{{/clusterprops.json:/metrics/history}} which overrides values specified in
{{solr.xml}}. Currently supported config options are:
** enable - boolean, default is true: enables collection of metrics history
(note that it's always possible to retrieve existing metrics history even when
enable == false)
** enableReplicas - boolean, default is false: enables collection of local
per-replica (core) metrics history
** enableNodes - boolean, default is false: enables collection of local node
and jvm metrics history.
** collectPeriod - int, in seconds, default is 60: metrics are collected and
updated this often.
** syncPeriod - int, in seconds, default is 60: in-memory DBs are persisted at
most this often (if modified).
> 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
> Attachments: 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: [email protected]
For additional commands, e-mail: [email protected]
