logary/logary

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.

Henrik Feldt

@haf

But I generally am fine with either way, again, as long as it's scriptable and it's easy to create nugets to release with it.

Joerg Beekmann

@jbeeko

Hi There. I've been trying use the ApplicationInsights target. I tried to replicate this script but open Logary.Targets.ApplicationInsightsdoes not compile because ApplicationInsights is not a module in the Logary.Targets namespace. What am I missing?

Joerg Beekmann

@jbeeko

Never mind, I see now I need to get the Logary.Targets.ApplicationInsights package. I expect with that I'll get further.

btrepp

@btrepp

I may be missing something obvious here, but is there a point free constructor for the message factory?.
LogLevel -> Message
but all the functions to make a message is of the form
message.event ->LogLevel->string->Message
So I feel like I have to write
do! Logging.log Info (fun l -> Message.event l "template |> Message.setField...)
I'd much rather
do! Logging.log Info (Message.fromtemplate "template >> Message.setField ... )

It also leads me to believe I'm possibly created log entries the wrong way?.

Jimmy Byrd

@TheAngryByrd

@btrepp do you have Message.eventInfo and friends? Should be similar to what you want. I've also just been using logSimple as it uses the Messages LogLevel

Jimmy Byrd

@TheAngryByrd

if I want to create a rule for a specifichiera like Npgsqland set it to Info and leave the rest as Debug how would I go about that? This doesn't seem to work for some reason.

                Rule.createForTarget ("console")
                |> Rule.setHieraString "Npgsql"
                |> Rule.setLevel LogLevel.Info
                Rule.createForTarget ("console")
                |> Rule.setLevel LogLevel.Debug

btrepp

@btrepp

@TheAngryByrd I've seen them, but they seem to curry it even more
Eg the log factory would want to ignore the first argument of log level.

Atm I've been creating point free like functions as needed, but I'm still trying to figure out what would be 'idiomatic' logary

Tbh it seems like most people would use logSimple, but I'm actually inside a Hopac Job, and waiting for it to at least be buffered or committed is the behaviour I am chasing

btrepp

@btrepp

Ahh it seems to be called Message.eventX

Henrik Feldt

@haf

@btrepp logger.info (eventX "Thing {happened}" >> setField "happened" 42)

That buffers in the job scheduler.

logger.infoWithBP buffers in RingBuffer ahead of each target (and you can continue/job is done) after ALL targets have this message in their ring buffers (but not taken it yet)

logger.logWithAck gives an Alt which gets committed when the RingBuffer of all targets has accepted the message and its inner value is a promise that gets committed/a value when all targets have flushed the log message.

You need to open the Message module in Logary to get the 'nice idiomatic` usage.

btrepp

@btrepp

Thanks @haf.

btrepp

@btrepp

Really digging those Ack/Hopac based methods, most of where I want logging is in the IO realm, which I'm using hopac jobs as a surrogate for

btrepp

@btrepp

Is it possible to use the shipper to ship logs to a process that stores them all in an SQL database? It seems this might be possible with the Rutta process?, is there a binary available or do I need to compile it?

btrepp

@btrepp

ah looks like the SQL target doesn't support serviceNames, so I might have to add that first

btrepp

@btrepp

Does current master build?. I'm getting errors when running the bundle exec rake

:\msys64\home\beau.trepp\net\logary\examples\Libryy\Libryy.fsproj: error : C:\msys64\home\beau.trepp\net\logary\examples\Libryy\Libryy.fsproj: C:\msys64\home\beau.trepp\net\logary\examples\Libryy\Libryy.fsproj could not import "$(FSharpTargetsPath)"
                Configuration: Release Platform: AnyCPU
BinaryAnnotation.cs(15,55): warning CS1570: XML comment has badly formed XML -- 'Reference to undefined entity 'rArr'.'

Granted i'm using msys2 on windows, so theres probably a whole bunch of hell with ruby interacting with it

Henrik Feldt

@haf

@btrepp Yeah, we got CI https://travis-ci.org/logary/logary/branches

Albeit not on Windows for Logary, because contributors haven't popped up on Windows.

Although you probably don't need to build the examples

btrepp

@btrepp

Ah I was going to try and get a dev environment up to try and do a PR for the migrations

You have a good point, I was just following the README and trying to initialize an environment to hack on :)

btrepp

@btrepp

Managed to get bits to compile, core tests run fine, DB tests throw {"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."} on the smoke test for what looks like an Sqlite in memory db on windows.

Henrik Feldt

@haf

@btrepp If I remember correctly those also get thrown from p/invoke on Win when you're running 32 bit code in 64 bit proc or vice versa.

btrepp

@btrepp

Mhmm I will have to play with that when I'm back at work and see what's going on

Is there any elegant way to wait for all the loggers to flush when I'm shutting down my application?

Henrik Feldt

@haf

Yes, there's a call called flush on the registry, but if you use the interface LogManager, Dispose() will wait for them all.

Ákos Lukács

@AkosLukacs

Hi !

Ákos Lukács

@AkosLukacs

Ah, so not compatible with NodaTime 2

Henrik Feldt

@haf

Hi there

Not yet, but soon

Tuomas Hietanen

@Thorium

what is the preferred workaround if I want to compile same web-server logic with .Net Framework and .Net Core, if I'm using Logary quite heavily? Should I just mock Logary calls with conditional compilation to aspnet-core-logging-dependency-injection-mess ?

Grégoire Lejay

@Antobiotics

Hi! Im quite new to f# but i'm encountering issues using logary im trying: ```

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?

btrepp

@btrepp

Anyone have any experience with the WinPerfCounters metrics? I've managed to get App metrics working (awesome), but half of the system metrics return 0

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

Ákos Lukács

@AkosLukacs

@Antobiotics Use NodaTime less than v.2.0

@btrepp share with us if you can get it working, thanks :)

Grégoire Lejay

@Antobiotics

@AkosLukacs thanks for the tip, I will try this out

Davydov Denis

@Inkp

Hello, would Logary support netcore anytime soon? I am on the crossroad between logary and serilog. Tried using net461 version on netcoreapp2.0 but it behaves oddly.

Ghost

@ghost~57bd5b1440f3a6eec0610e8d

Hi All, I would like to volunteer improving the build process. Requiring the Ruby environment on windows is a bit of a pain. I'd like to propose the use of FAKE and PAKET

Quintus Marais

@quintusm

It seems like a good idea to try and get rid of the Ruby requirement. I have run into a versioning issue myself trying to do a build with the newest version of Ruby...

btrepp

@btrepp

I might be lost here, but it looks like logary looks for a ToValue on unknown types, like Chiron with ToJson. Does anyone know how this works?. I suspected it might've been ToValue : 'a -> Value or ToValue: 'a -> Value<string> etc but I can't seem to get it compile

Where communities thrive

People

Repo info

Activity