[ https://issues.apache.org/jira/browse/SOLR-11779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475818#comment-16475818 ]
Andrzej Bialecki edited comment on SOLR-11779 at 5/15/18 1:23 PM: ------------------------------------------------------------------- Each RRD database takes ~30kB in the configuration proposed in the patch, which consists of 4 time-series: * 240 samples 60 sec apart (4 hours) * 288 samples 600 sec apart (48 hours) * 336 samples 1h apart (2 weeks) * 180 samples 4h apart (2 months) I'll attach example screenshots of graphs generated using {{/admin/metrics/history}} handler. Graphs are sent as base64-encoded PNG data, so they could be directly used by the UI in a data URI like this: {{data:image/png;base64,iVBORw0KG...}}. was (Author: ab): Each RRD database takes ~30kB in the configuration proposed in the patch, which consists of 4 time-series: * 240 samples 60 sec apart (4 hours) * 288 samples 600 sec apart (48 hours) * 336 samples 1h apart (2 weeks) * 180 samples 4h apart (2 months) I'll attach example screenshots of graphs generated using {{/admin/metrics/history}} handler. > 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 > > > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org