Logary is a high performance, multi-target logging, metric and health-check library for mono and .Net. Targets include: textwriter, console, debugger, nlog, zipkin, nimrod, riemann, logstash, sqlite, sql server, graphite, loggr, elmah.io, logentries. Adapters for: suave.
Is there any elegant way to wait for all the loggers to flush when I'm shutting down my application?
Not yet, but soon
let logger = Logging.getCurrentLogger ()
Message.event Info "Something here" |> Logger.logSimple logger
and getting :
threw an exception. ---> System.MissingMethodException: Method not found: 'NodaTime.Instant NodaTime.SystemClock.get_Now()'.
at Logary.MessageModule.Event(LogLevel level, String template)
(i apologize in advance if it's not the right place to ask)
i tried to add
NodaTime to my paket dependencies but that didn't work. Is there something obvious that i am missing?
Tried on server 2016 running as a service under nssm, and admin(UAC) on windows 10
Proccessor stats are all zero, along with memory
a few other system counters work, but mainly I was chasing the CPU and memory :D
@btrepp share with us if you can get it working, thanks :)
I'm sure theres some nice functions and I'm just not finding them
@btrepp the previous version of WinPerfCounter has some bug when use with more than one instance. the new version has solved this. you can see the detail in logary/logary@9bcfacd , the old version use
x.counter.InstanceName <- instance to change instance, this will initial the instance and the first NextValue is always zero.
@/all update the readme about the new version of logary : https://github.com/logary/logary/tree/feature/live-wpc-reconfigure#tutorial-and-things-around-message
So, this is weird. I'm not finding the methods I'm expecting in Logary.Configuration
Anyone experienced this before (and how do I go about fixing it?)
I'm after figuring out how much some low-level interop is called, and having a metric like x per second would be fine rather than smashing out heaps of individual messages
and there is a Metricconf.create method
But that takes some sort of metric constructor?. Do I have to memo this?. How would I tick values into a Counter?.
So I've noticed there's been a new release of hopac (yay), but logary stable hasn't been updated in a while (okay).
Unfortunately the latest published hopac and logary don't play nice.
Unhandled Exception: System.TypeInitializationException: The type initializer for 'Program' threw an exception. ---> System.TypeInitializationException: The type initializer for '<StartupCode$Epsilon>.$Program' threw an exception. ---> System.MethodAccessException: Attempt by method 'Logary.Supervisor.create(Logary.Logger)' to access method 'Hopac.Job+Global.startIgnore<Microsoft.FSharp.Core.Unit>(Hopac.Job`1<Microsoft.FSharp.Core.Unit>)' failed.
at Logary.Supervisor.create(Logger logger)
at Logary.Registry.Advanced.create(LogaryConf conf)
at Logary.Configuration.Config.RunLogary(LogaryConf conf)
at Logary.Configuration.Config.WithLogary(String serviceName, FSharpFunc`2 fConf)
at <StartupCode$Epsilon>.$Program..cctor()
--- End of inner exception stack trace ---
at Program..cctor()
--- End of inner exception stack trace ---
at Program.main(String[] _arg1)
Locking to 4 logary keeps me working for now. I would like to upgrade to 5, but currently the beta tag worries me
(I'm a little wary after freyas 4 being rc for over a year)
@btrepp v5 is currently much more stable; it's beta because the licenses need sorting out. See logary/logary#351
bug?
Just playing around with the docs to further consolidate Logary in my head, here's the code-snippet
[<EntryPoint>]
let main argv =
use logary =
withLogaryManager "logary test" (
withTargets [
Console.create Console.empty "console";
InfluxDb.create influxConf "influxdb";
]
>> withRules [
Rule.createForTarget ("influxdb");
Rule.createForTarget ("console");
]
) |> Hopac.Hopac.run
let logger = Logging.getCurrentLogger()
let lFun = fun infoEvent -> Logger.log logger LogLevel.Info (fun _ -> Message.eventInfo infoEvent)
let l =
job {
do! lFun "Logary is weird 1"
do! timeOutMillis 10 // need a small delay, or it doesn't work
do! lFun "Logary is weird 2"
}
Stream.indefinitely (l <*> (timeOutMillis 5000 )) |> Stream.consumeIf you log two things in quick succession to the influx target, you lose 'one' of them