Ah finally some sort of breakthrough, thanks @jberzy . I had been looking at configuring the endpoints in the portal. I changed the http port 80 to the akka.net port it is listening on. and this worked. Worked in that, it certainly received something, but on the listener, it throw an error with "Dropping message [Akka.Actor.ActorSelection] for non-local-recipient". But this is fine, this is due to the server not being able to communicate back to a publicly available IP (which is the client).
grafana looks nice, but looks like it has some of the same problems that cactus does.. the numerical information is not presented well, and while the graphs are prettier than cactus it's still kind of generic.
@annymsMthd thanks! it was good seeing you guys, thanks for coming to the meetup
@rodrigovidal@trbngr@shersh thanks guys, glad you liked it!
@Mystere Hystrix looks interesting. Right now we support StatsD, as @Horusiath mentioned
@ianbarry would it be helpful if @skotzko and I put together some DevOps videos for that sort of issue?
we've been getting asked about that sort of stuff from a lot of folks who've just started using Akka.Remote / Akka.Cluster
@Aaronontheweb That would be awesome if you could do that. I felt the barrier to entry on getting started with akka.net was really low and the petabridge bootcamp has greatly helped with that. And then I came across remote and clustering between machines as being a bit more of a barrier, when getting down and dirty and trying to apply it to what I needed, with any examples pointing at localhost on the same machine. Thanks! :smile:
@ianbarry yeah, I know what you mean. The DevOps overhead for any applications that depend on sockets rather than HTTP goes up considerably
I had to learn a lot of that stuff the hard way and it really sucked
I'd rather make it easy for everyone else :p
@Aaronontheweb awesome, thank you and I'm sure many others will be grateful too! I'm kinda feeling this pain at the moment. But I am now seeing the light :)