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.

Jared Hester

@cloudRoutine

@haf the manual approach to modifying the Logary.Facade seems like more of a hassle than it needs to be
could you make a nupkg just for it that installs it as a template file?
https://docs.microsoft.com/en-us/nuget/create-packages/source-and-config-file-transformations

Henrik Feldt

@haf

@cloudRoutine Does that work with paket, too?

@endeavour Afraid not, noone stepped up to maintain it and I stopped using it myself.

It's easy to upgrade though; just get cracking and ask any questions you have here.

fsprojects/Paket#1139 @cloudRoutine

Jared Hester

@cloudRoutine

@haf aww that's a shame, you could still do it for those odd ducks who insist on sticking with Nuget though :laughing:

Henrik Feldt

@haf

@cloudRoutine I wish a knew someone like that ;)

Jared Hester

@cloudRoutine

i'll look into fixing paket to support it, but you'll have to make the template yourself :P

Henrik Feldt

@haf

@cloudRoutine Will do if you fix up Paket support ;)

Jared Hester

@cloudRoutine

:+1:

James Freiwirth

@endeavour

I have a dumb question. What is the RabbitMQ target actually for?

It just dumps log messages onto rabbitMQ? Am I then responsible for writing something that subscribes to it and writes them into a database/elasticsearch etc?

Duncan Mak

@duncanmak

hello all

I saw this note, SuaveIO/suave#574, what should I do if I wanna add logging to my tiny Suave v2 app?

Henrik Feldt

@haf

@duncanmak , @adamchester gave you a sample back in the suave chat :)

Duncan Mak

@duncanmak

nice!

thanks!

Kolja Dummann

@coolya

would a azure application insights target be welcome? I'm writing one as side project right now.

Adam Chester

@adamchester

@coolya I would say yes definitely

James Freiwirth

@endeavour

@coolya Yeah I'd like that too :)

dylanbevandotnet

@dylanbevandotnet

Dumb question here as I'm new to Logary. If I want to keep track of something like the number of users that log in, I don't see how I can update the metric. Say I have a log in method, I want to increase the value by one, not keep track of how many are already there. The samples show a metric that is constantly pumping out values (with knowledge of the last value) but doesn't indicate how I'd push a value to it from another location. i.e. let login userName password = ..validate credentials. tell logary that someone has logged in

Henrik Feldt

@haf

@dylanbevandotnet The Message types with a metric value, like Gauge will be sent to your targets. You can either create them via Logger from your login function, or you can have a Metric instance that aggregates logins every tick

There's a presentation on channel 9 by me about Logary and this exact feature

dylanbevandotnet

@dylanbevandotnet

Thanks @haf , I had a momentary brain fart. After I posted I realized that it was up to the target to aggregate. Thanks for the video pointer I'll go check it out.

dylanbevandotnet

@dylanbevandotnet

Ok so new question now. If I have a popular shopping site and I declare an event that happens everytime someone buys a product (Message.Event Info "{item} Purchased"), what are my options for creating a derived metric that could aggregate the total number of purchases in the tick interval, as well as the counts per item? Basically do I have to increment a specific item purchased gauge AND send an event (to get full details), with a derived metric accumulating all the specific item gauges.
OR can I create derived metrics off the event. I'm not seeing a way to do that through the API but maybe I'm missing something obvious. Thanks

Henrik Feldt

@haf

@dylanbevandotnet You can either pass the values to a Metric, which in turn yields Derived values. There's a sample of that in the samples folder/project. Or you can create a Message every purchase with the data you need and have the targets ship to where you need; like Influx – and let Influx do the aggregation for you.

Tuomas Hietanen

@Thorium

I made a PR for AppInsights. If you have ideas how to also use AppInsights performance logging measurement features, that would be nice. Now it's just creating bulk trace items.

And that should be released as a separate nuget package I suppose, as it creates a new dependency

Henrik Feldt

@haf

Thanks @Thorium

I've replied to your architecture question

James Freiwirth

@endeavour

Is there a way to automatically add a field to every log message?

Henrik Feldt

@haf

Yes

Middleware.

With config or with Logger

Logger.apply (setFieldName "myField" myobj) logger

or Config.withMiddleware

Jimmy Byrd

@TheAngryByrd

@haf what's your preference for netfull/netstandard support? 1 fsproj to rule them all or two separate fsprojs, 1 old 1 new with mergenuget thing?

Henrik Feldt

@haf

Hi there. I prefer a single command to build them both, if that command isn't buggy....

I saw Alfonso complaining the other day about interference between different .net core sdk versions when building

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.

Where communities thrive

People

Repo info

Activity