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

@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

btrepp

@btrepp

Ah it seems that the static inference in F# is pickier than I would imagine. Method needs to be defined a ToValue (x:_) : Value<unit>. Returning a function is not enough for the F# compiler

btrepp

@btrepp

What's the best way of timing an Alt<_>? It strikes me as maybe a Message.timeAlt is the case, but the Logger.log function doesn't really gel with the types (unless I create factory functions to ignore or set the messages)

I'm sure theres some nice functions and I'm just not finding them

Jun

@lust4life

@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

Tuomas Hietanen

@Thorium

I have ideological reasons to not install any non-functional-first-programming-language-environments to my machine (aka. now it works, I don't want to break it). So one more vote for getting rid of Ruby.

Aleksander Heintz

@Alxandr

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?)

btrepp

@btrepp

How do the counters work in logary 4.2.1?

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

btrepp

@btrepp

So I've deduced the model appears to be creating a metric and pushing values in with update, and summarizing per 'tick'

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?.

btrepp

@btrepp

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)

Henrik Feldt

@haf

@btrepp Thanks for reporting. This is accurate. There's a doc/issue about this in the issue tracker (perhaps you)

btrepp

@btrepp

Wasn't me, think someone independently found it.

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)

Where communities thrive

People

Repo info

Activity