Discoverable modules and the new module registry #559
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR brings back something we had back in Kamon 0.6.x: the ability to discover modules by simply having them in the classpath. From this point on, calling
Kamon.loadModules()
will pick everything under thekamon.modules
configuration and try to start them.We didn't have the actual "modules" concept in 1.x, only reporters were available but with this PR the MetricReporter and SpanReporter traits are just a special type of module. Soon we should be moving things like the executor metrics collectors and JVM/host metrics to modules so that we can globally control their lifecycle and allow a "drop a jar" installation method :).
Also deprecated the "addReporter" variants but kept them compatible.