ensure that the datadog module works on Windows about kamon HOT 17 CLOSED

@labrg I did some testing today with a Windows machine and all metrics were reported correctly.. One thing that I noticed is that by default the agent was only listening on 127.0.0.1 and my application which was running on another host wasn't going to reach it. I had to add the option bellow to datadog.conf to make sure that it was listening on 0.0.0.0 and after that all metrics starting showing up.. might it be possible that you have a similar problem?

non_local_traffic: True

from kamon.

@ivantopo The Akka Standalone Application is kicked off by the microkernel from the command line on my local machine. The agent is also running on the local machine. Did you test a standalone app with the Windows agent and have success?

from kamon.

@labrg do you have any example project that I can use to test?

from kamon.

@labrg I did some tests with the akka microkernel example and I can see the metrics being published to datadog. I had to touch a little bit the akka.bat file to include the aspectj weaver and it ended like this:

@echo off

set AKKA_HOME=%~dp0..
set JAVA_OPTS=-Xmx1024M -Xms1024M -Xss1M -XX:MaxPermSize=256M -XX:+UseParallelGC
set AKKA_CLASSPATH=%AKKA_HOME%\lib\scala-library-2.10.4.jar;%AKKA_HOME%\config;%AKKA_HOME%\lib\akka\*

C:\jdk1.6.0_23\bin\java -javaagent:C:\akka-2.3.4\lib\akka\aspectjweaver-1.7.4.jar %JAVA_OPTS% -cp "%AKKA_CLASSPATH%" -Dakka.home="%AKKA_HOME%" akka.kernel.Main %*

We introduced a small change that produces a big warning if you don't start your application with the aspectj weaver, if it is possible to you, please build from master and try with that to make sure that there are no problems with your aspectj weaver setup.

from kamon.

@ivantopo Thanks, I was going to test using the microkernel example, but got busy with a few other things. I had made those changes in akka.bat and I can see the weaver working fine. I'll try building from master and see if there's something missing. Please allow me some time to get back to you.

from kamon.

@ivantopo Hi, I did try the microkernel example with datadog on my home PC (Win 7) with the build from master. Again, same results. Here's a link to my files/settings:
https://drive.google.com/folderview?id=0B5cvYHPFpSxZendHbDczOFU5SGM&usp=sharing
I'd appreciate it if you could test and see if you succeed in publishing the metrics.

from kamon.

@labrg can you please list the contents of the lib folder?

from kamon.

@ivantopo lib\akka\aspectjweaver-1.8.1.jar was added to the existing akka dist download (2.10_2.3.4)
I used maven-assembly to package a jar-with-dependencies and put it in the "deploy" folder.

from kamon.

@labrg I tested your application on my windows server VM and it worked just fine, here is a screenshot of what it reported to Datadog over the last hour or so... there must be something else on your setup that is making it fail and since the metrics are just thrown out via UDP is a bit harder to determine what is wrong.. I'll try to find someone with a Windows 7 machine and try again there, but that might take some time. One more thing to test: If you capture the traffic on your local machine, using something like Wireshark, are you seeing the metric packets?

from kamon.

@ivantopo First of all, thank you again for taking the trouble to help me through this issue. I ran RawCap (http://www.netresec.com/?page=RawCap) to sniff "localhost" and sent a packet using 'nc' from cmdline. Here's a snippet of the RawCap generated output file opened in Wireshark:

However, I can't capture similar UDP packets when running my application. DogStatsd never receives the packets.

The weaver is weaving the Kamon classes but nothing else. I've shared "kamon-weaver.txt" for the weaver logs during my application run, in that google drive folder that I had posted earlier.

from kamon.

@labrg quick question, when you use nc and other command line tools, how did you get them? are you using cygwin I guess?

from kamon.

@ivantopo I'm using cmder. (https://github.com/bliker/cmder), but it doesn't have netcat. Someone had netcat available for Windows: https://drive.google.com/folderview?id=0B5cvYHPFpSxZV1hMUUYxT2tpWHM&usp=sharing

I installed Datadog 5.0.0 BETA (https://gist.github.com/remh/1426ccb24ec36162ba2b) on our Redhat server (it is self-contained, so it didn't require us to upgrade Python). Still some issues with DogStatsd that I have contacted their support about. I'll be testing the application on there as well and keep you updated.

from kamon.

@labrg I just tested this on a Windows 7 machine and it worked without any issues, that is good news for us because I'm sure that it works on Windows 7 now, but bad for you because it doesn't solve your issue... My last guess would be some sort of antivirus that might be blocking the traffic from the application, but surely is something on the environment and not the module itself. Hopefully you will have luck when trying on Redhat, hope to hear your feedback on that, best regards!

from kamon.

@ivantopo Hello, I had no luck with our Redhat server. I also tested 'eigengo' (https://github.com/eigengo/monitor) today following this great article (http://java.dzone.com/articles/monitoring-akka) and again, I couldn't get it to work with Datadog. Thanks for all your help. I think this issue should be closed now.

from kamon.

@labrg add me on google hangouts: [email protected] and let's chat to see if there is any way in which I can help you, thanks for your efforts and time!

from kamon.

@ivantopo Here's what I found:
I had used maven assembly plugin to package an application jar-with-dependencies that was placed in "deploy" folder, and I had left Akka standalone's "lib" folder unchanged. This runs without any complaints, but fails to report application metrics to Datadog.

However, it seems that all the jars for Kamon and its dependencies need to go in the "lib" folder. When I did so, the metrics are reported just fine! In this case, the application jar-with-dependencies in the "deploy" folder still did include Kamon and its dependencies.

from kamon.

@labrg I'm really happy to know that this finally worked out for you! Thanks for the information and for all the time you've spent dealing with this issue.. I still would like to dig more details on why this happened and document it for future users but that will have to wait a bit.. hope that you have fun with Kamon and share your experience with us!

from kamon.