[
https://issues.apache.org/jira/browse/BLUR-67?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629004#comment-13629004
]
Tim Williams commented on BLUR-67:
----------------------------------
Ok, then maybe our own Reporter abstraction that gets access to the
configuration? e.g.
BlurMetricsReporter(MetricsRegistry registry, Configuration conf)
Then, classes on (blur.metric.reporter.classes) must implement that
abstraction? e.g.
GangliaBlurMetricsReporter extends BlurMetricsReporter {
private GangliaReporter internalReporter;
public GangliaBlurMetricsReporter(MetricsRegistry reg, Configuration conf) {
internalReporter = new GangliaReporter(...params retrieved from conf...);
}
}
I'm not that pressed either way, javascript in the props file just felt a
little weird that's all.
> Add config options for metrics reporters
> ----------------------------------------
>
> Key: BLUR-67
> URL: https://issues.apache.org/jira/browse/BLUR-67
> Project: Apache Blur
> Issue Type: Bug
> Affects Versions: 0.1.5
> Reporter: Aaron McCurry
> Fix For: 0.1.5
>
>
> The default metrics reporter is JMX per JVM. However there is no way for the
> metrics to be configured with another reporter such as ganglia.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
