-
Notifications
You must be signed in to change notification settings - Fork 328
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Play's application.conf ignored by Kamon when I load the kamon-akka module #343
Comments
@gaelrenoux the you can try with |
Thanks for the advice, I removed the Kamon.start and Kamon.stop. I got some time to look a bit more into it, I uploaded a sample application here. It works fine as is. But uncomment kamon-akka in build.sbt, and you have a problem on startup where it doesn't find application.conf. I tried the following but it didn't help : |
This is probably related: |
@gaelrenoux sorry for the late response ;(, but If you run the example with |
I have a Play application (with Scala). In one controller, I inject the actor system and start a few actors to accomplish background tasks.
I have just set up Kamon (0.6.0) with Statsd, Graphite and Graphana as the back-end. With these modules, everything works fine:
I use the aspectj-play-runner plugin and start my application with aspectj-runner:run. The Kamon.start() is in the Global.onStart(Application) method.
However, as soon as I add kamon-akka in my build.sbt, Kamon seems not to be able to read the configurations values in conf/application.conf any more. I have put a debug point in SimpleMetricKeyGenerator (when it reads "kamon.statsd.simple-metric-key-generator"):
Play still has access to the values in conf/application.conf, though.
The text was updated successfully, but these errors were encountered: