These are chat archives for akkadotnet/akka.net

28th
Aug 2015
Garrard Kitchen
@garrardkitchen
Aug 28 2015 10:18
What's the best approach if an actor at the end of a hierarchy requires a value normally / best passed in via the constructor [this could be a ref to a remote actor]? Do I pass it down via each child until I hit the actor that needs this value?
tstojecki
@tstojecki
Aug 28 2015 12:14
@garrardkitchen ActorSelection might do the trick, it has .Tell on it
Garrard Kitchen
@garrardkitchen
Aug 28 2015 12:48
@tstojecki Thanks for response. I chose to go the DI route in the end as the values that this actor required were one off initialisation values for that actor. The thing I really wanted to avoid was having to pass the same values through all actors all the way down to the actor that needed them, so job done I think. Maybe if one of these values becomes a variant in the future then I'll use the ActorSelection approach instead.
Roger Johansson
@rogeralsing
Aug 28 2015 17:16
So mono + docker and Akka.NET, anyone had any success with this setup?
@garrardkitchen are there some specific messages that get that big?
@garrardkitchen if that is the case, I'd suggest to make a special serializer for those, translate the message to binary using e.g. json.net or whatever, and then compress the message using Gzip. to the From and ToBinary methods of the akka serializer can pack and unpack the message
Garrard Kitchen
@garrardkitchen
Aug 28 2015 17:23
@rogeralsing Thanks for reply. This is what we had done prior to this and yet still the payload was larger than 128k! It's working as designed so all is good
Roger Johansson
@rogeralsing
Aug 28 2015 17:23
oki :+1:
Garrard Kitchen
@garrardkitchen
Aug 28 2015 17:24
@rogeralsing docker & akka.net is another thing I've been itching to do. I feel I may have to scratch that one soon!
Roger Johansson
@rogeralsing
Aug 28 2015 17:34
Everyone, there was some questions after our last meetup asking about logging to the ELK stack... I've since then started to build better support for semantic logging.
elasticlog.png
I've created a custom logger that parses log messages of the old string.format style, so we can get semantic logging for all of akka.net, even the internals
so we can do diagnostics based on the built in log messages
this log will also include the origin of the log entry so if you use elasticsearch for an akka.net cluster, you will know what node that wrote that specific entry
Garrard Kitchen
@garrardkitchen
Aug 28 2015 18:06
@rogeralsing Excellent! I had been using serilog-sink-ES to get semantic logging but this was outside of the akka logger so great to read that this is now built in!
Roger Johansson
@rogeralsing
Aug 28 2015 18:09
The problem with serilog in Akka.NET is that it works fine for user code, where you explicitly use a log template e.g. "Log stuff {SomeMetric} and {SomeMore}" , but akka.nets internal logging uses string.format based templates . "log {0} and {1}" which results in useless data for elasticsearch as the values are not named... the new logger solves that.
David Flerlage
@davidflerlage
Aug 28 2015 23:51
Hey everyone, I'm looking into the outstanding issue with the PostgreSQL persistence plugin. Is anyone here knowledgeable about the akka.net build servers?