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.
In message templates,
IPAddress would be stringified early in the process
I am using expecto
You'll need to run the FacadeAdapter to change expecto to use Logary also.
file target*
a logger is just a reference to the logging infrastructure.
It's up to the logging infra to choose where to write
is there a straight and simple example of getting the Expecto.Logging.TextWriterTarget or whatever is needed to write to a string buffer or to a file called "application.log"?
am I going about it wrong? I just want the text results of the test run so I can both save it to a text file and do a simple parse and format.
open Expecto
[<EntryPoint>]
let main argv =
use logFile = new System.IO.StreamWriter("testlog.txt")
Logging.Global.initialiseIfDefault
{ Logging.Global.defaultConfig
with getLogger = fun name -> Logging.CombiningTarget(name,
[ Logging.TextWriterTarget(name, Logging.Verbose, logFile)
Logging.LiterateConsoleTarget(name, Logging.Verbose) ])
:> Logging.Logger
}
Tests.runTestsInAssembly defaultConfig argv
@haf the manual approach to modifying the Logary.Facade seems like more of a hassle than it needs to be
could you make a
https://docs.microsoft.com/en-us/nuget/create-packages/source-and-config-file-transformations
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
@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
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?
I saw this note, SuaveIO/suave#574, what should I do if I wanna add logging to my tiny Suave v2 app?
thanks!
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
There's a presentation on channel 9 by me about Logary and this exact feature
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
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
@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.
And that should be released as a separate nuget package I suppose, as it creates a new dependency
I've replied to your architecture question