Skip to content
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

Monitoring for Futures #62

Open
vatel opened this issue Nov 6, 2013 · 1 comment
Open

Monitoring for Futures #62

vatel opened this issue Nov 6, 2013 · 1 comment
Assignees

Comments

@vatel
Copy link

vatel commented Nov 6, 2013

Hello!
Many applications use Futures intensively - do you have plans to implement their monitoring?

P.S. I have posted a question and some thoughts about it to the blog: http://www.cakesolutions.net/teamblogs/2013/11/01/monitoring-akka/

@janm399
Copy link
Member

janm399 commented Nov 7, 2013

I would like to include code that monitors the Dispatchers in the first instance. That will give you the insight into how your actor system is consuming the available threads. And it will be especially useful when you have blocking calls, and you’ve created multiple Dispatchers to isolate the blocking calls. I think this is the only way to deal with monitoring Futures: I would like to be able to see the execution time & timeouts.

The transforms map, flatMap and others I think fall into a general code monitoring category. Your best bet to track the performance of these is to use some JDK profiler at development. It would be really difficult to display the data in a meaningful way to the operations team.

@ghost ghost assigned janm399 Nov 7, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants