search

datalust / seq-tickets

Issues, design discussions and feature roadmap for the Seq log server
https://datalust.co/seq
97 stars 5 forks source link

All guids show in "legacy" format? #212

Closed bytenik closed 10 years ago

bytenik commented 10 years ago

Ever since upgrading to 1.5, all my GUIDs show in a format similar to:

UuidLegacy:0x00af9c77e8d62443589833c698a7d108

Can this be put back (or changed via a setting) into registry format, like Seq used to show?

nblumhardt commented 10 years ago

Wowsers! I've never seen anyhing like that?! :-S

Do you mean logged GUIDs in properties? Here's one straight out of my own 1.5 install:

image

Since the conversion to a string happens on the Serilog side it's possible there's some change in the JSON formatting there (as you'd have noticed, the Seq client for Serilog moved to Serilogs.Sinks.Seq. I'll investigate that angle now.

nblumhardt commented 10 years ago

Just ran my test bench with:

Log.Information("{Uuid}", Guid.NewGuid());

Came through fine, just like the example above. (Latest Seq and Serilog.)

Any other clues?

nblumhardt commented 10 years ago

@bytenik any other clues? The only mention I can find anywhere of this format is in relation to MongoDB - I don't suppose you have a Mongo-specific GUID representation being serialized through the logger?

bytenik commented 10 years ago

Oy, it appears that may be what is happening. The type appears to have an implicit Guid conversion which is why I never picked up on the fact that its a different type!

Sorry for wasting your time.

nblumhardt commented 10 years ago

Not a problem, thanks for the report and follow-up. Each oddity like this adds another recipe to the problem-solving cookbook :)