petabridge / akka-monitoring Goto Github PK

Hello,

Do you have any ideas on how we would measure time spent in the mailbox before processing? I easily am measuring the time to process the messages (I have a PR coming with some nice additions to make this easier).

Also other things I wanted were things like a guage of the number of messages in the mailbox, I wish we could have something like http://kamon.io but that would rely on .NET having some useful instrumentation support like Java does here's hoping one day this can be a reality withing diving into the Profiler API.

Cheers
Stefan

Build files are outdated.
This will require us to change from packages.config to package references

Steps to reproduce:

1. Ensure Akka category name DOES NOT exists in PerformanceCounters
2. Start demo app as admin with default configuration:
   ActorMonitoringExtension.RegisterMonitor(actorSystem, new ActorPerformanceCountersMonitor(customMetrics));
3. Ensure Akka category name exists in PerformanceCounters
4. Stop demo app
5. Add custom counters to the demo app, eg.:
   var registeredMonitor = ActorMonitoringExtension.RegisterMonitor(_system, new ActorPerformanceCountersMonitor( new CustomMetrics { Counters = { "akka.custom.metric1"}, Gauges = { "akka.messageboxsize"}, Timers = { "akka.handlertime" } }));
6. Start demo app as admin.

Expected: new performance counters "akka.custom.metric1", "akka.messageboxsize" and "akka.handlertime" created and seen in Performance Monitor

Actual: new performance counters are not created

When running the performance counters initialization the second time around (when the performance counters already exist) the application fails at perfmon registration time. This is due to elevated privileges required in order to remove a performance counter.

I have added Akka.Monitoring along with the ApplicationInsights plugin to our project. I noticed that since we also use Akka.Persistence (with 1000's of events in the event journal) we have a lot of messages flying around on startup, as well as a lot of debugging being logged. It seems that every message from the event journal is getting logged on startup to AppInisghts.

I was wondering if there are anythings one can do to configure this behaviour? I would possibly like to disable logging all "akka.logging.debug" messages and maybe also disable messages that happen during replay of events.

Let me know what the best approach is, or if some of this is already supported.
Thanks

I'm using the StatsD monitoring package (Akka.Monitoring.StatsD 0.7.0).

I'm getting the following warning:

"warning NU1701: Package 'Akka.Monitoring 0.7.0' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.0'. This package may not be fully compatible with your project."

Can you guys recompile targeting .Net Standard 2.0?

Based on some benchmarks I performed in another project that consumed Akka.Monitoring.PerformanceCounters, this monitoring implementation itself may act as a major performance bottleneck due to the high-contention of its monitoring sinks. This should be redesigned to suit a more asynchronous and low-overhead approach and will necessitate the use of NBench and other tools.

This will allow us to set the server config in code