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.
Short term easy solution might be
TextWriterTarget -> simple nlog adapter
if you have an idea of the goal and issues involved in
Message->String it would be great if you can write down some ideas in a github issue? :+1:
maybe
TextWriterTarget is still a decent option, just that we don’t expose a way to create a decent custom formatter yet
(because as you mentioned, the template stuff is internal)
So text writer won't help here, you do need message->string in a format suitable for text loggers
I'll go try it out, and I'll think about the possible Message->String function goals. Thanks a lot for the help!
Hi. I'm having some trouble installing Logary using Paket. The required Hopac version requires a newer FSharp.Core than Logary and Suave
Paket the atempts to resolve the versions, printing messages like:
Could not resolve package FSharp.Core:
- Hopac 0.3.23 requested package FSharp.Core: >= 4.0.1.7-alpha
- Logary 4.0.112 requested package FSharp.Core: >= 4.0.0.1 (no prereleases)
- Suave 2.0.0 requested package FSharp.Core: >= 4.0.0.1 (no prereleases)It ends up on Logary 4.0.112 and Hopac 0.3.14
Paket version 3.33.3
Main FAKE - 4.48
Main Logary - 4.0.112
Main Newtonsoft.Json - 9.0.1
Main SQLProvider - 1.0.41
Main Suave - 2.0Mono 4.6.2
Is this a known issue?
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!
