From f1c6ceffa22c59a463d6d8cd2ca77e2b440eb450 Mon Sep 17 00:00:00 2001 From: Ivan Topolnjak Date: Mon, 29 Oct 2018 17:45:57 +0100 Subject: Implement a module registry that supports loading from configuration (#559) --- kamon-core/src/main/resources/reference.conf | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) (limited to 'kamon-core/src/main/resources/reference.conf') diff --git a/kamon-core/src/main/resources/reference.conf b/kamon-core/src/main/resources/reference.conf index 2fa3d33b..0fb3ce0a 100644 --- a/kamon-core/src/main/resources/reference.conf +++ b/kamon-core/src/main/resources/reference.conf @@ -25,11 +25,22 @@ kamon { } } - # FQCN of the reporter instances that should be loaded when calling `Kamon.reporters.loadReportersFromConfig()`. All - # reporter classes must have a default constructor. No metric filtering is applied to metric reporters started this way. + # Modules that can be automatically discovered and started by Kamon. The configuration for each module has the + # following schema: + # + # kamon.modules { + # module-name { + # enabled = true + # class = "com.example.ModuleClass" + # } + # } + # + # All available modules in the classpath are started when calling Kamon.loadModules() and stopped when calling + # Kamon.stopModules(). + # + modules { - # Example: `reporters = ["kamon.prometheus.PrometheusReporter", "kamon.zipkin.ZipkinReporter"]`. - reporters = [ ] + } # Pool size for the executor service that will run sampling on RangeSampler instruments. This scheduler is accesible # through Kamon.scheduler() -- cgit v1.2.3