Hi. I'm evaluating Akka.net, and I'm trying to figure out on what level to use it in a WPF application. I cannot find any solid info about it, so I hope to get some input here.
As it stands, I'm using an CQRS approach, in which I send commands to PersistentActors, and PersistentView (to be PersistenceQuery I believe) to get the data. Is it "the wrong way" to have my viewmodel depend on the IActorRefFactory, and create the View/Query actor to populate the viewmodel with data?
Hello I would like to know when I have this in my App.Config file
akka { stdout-loglevel = DEBUG loglevel = DEBUG log-config-on-start = on actor { debug { receive = on autoreceive = on lifecycle = on event-stream = on unhandled = on } }
Do I need to call _log.Debug("Some message"); in my Actors? Or Akka take cares of that for me.
Please can anyone advice me on that.
akka.remote.log-remote-lifecycle-events = off
while the setting removed some things, it didn't really remove the most "spammy" cluster ones. I seemed to have managed to filter them out via nlog though:
<rules>
<logger name="*" minlevel="Debug" writeTo="console">
<filters>
<when condition="contains('${message}', 'Received Akka.Cluster.GossipStatus')" action="Ignore" />
<when condition="contains('${message}', 'Received Akka.Cluster.GossipEnvelope')" action="Ignore" />
<when condition="contains('${message}', 'Cluster Node') and contains('${message}', 'Receiving gossip from')" action="Ignore" />
</filters>
</logger>
</rules>
I do think it would be a nice feature to have a "master switch" of some sort that turns the framework debug logs on/off rather than having to manually filter them or just use Info+ in your app.
You do not need to specify /user at the start of each path. It is implied.
which very much seems false as the message goes to dead letters rather than the routee when I leave the /user
prefix out.
Cluster.Down
for the unreachable node
Down
and Leave
is that Leave is graceful; Down is for forcing the cluster to evict a node if it's died and is never coming back
ReadView
internal?
CurrentClusterState
instead now - it's exposed as a public readable property on the Cluster
object