NChronicle/NChronicle.Core

Issues

• As a developer, I want to include a stack trace on all records, so I can track down the call sites

  #15 opened 4 years ago by kana-ki
  0

• As a developer, I want NChronicle to Support Windows Performance Counters, so I can monitor/query the metrics of errors/logs in my application.

  #19 opened 4 years ago by kana-ki
  0

• As a developer, I want to persist logs as ETW events, so I can utilise high performance and windows collected logging

  #18 opened 4 years ago by kana-ki
  0

• As a developer, I want to persist logs to sentry, so I can gather them in one place with other logs and have them accessible via a web UI

  #17 opened 4 years ago by kana-ki
  0

• As a developer, I want to template record messages, so I can have a single repository of abstract messages

  #16 opened 4 years ago by kana-ki
  0

• As a developer, I want structured logging, so I can read the logs back programatically

  #14 opened 4 years ago by kana-ki
  0

• As a developer, I want to provided arguments for my message, so I can attach meta information and render them in messages

  #13 opened 4 years ago by kana-ki
  0

• As a developer, I want to be able to persist tags through all records in a scope, so I can ensure common tags in that area are used.

  #12 opened 4 years ago by kana-ki
  0

• As a developer, I do not want exceptions in logging to stop execution of my block/thread/app, so my code can continue to completion.

  #11 opened 4 years ago by kana-ki
  1

• Rename NChronicle to Chronicle so it can be used without the explicit NChronicle namespace

  #3 opened 4 years ago by kana-ki
  0

• Move FormulateOutput to NChronicle.Core

  #7 opened 4 years ago by kana-ki
  0

• As a user, I want to scope accross chronicle instances, so that I can use another class that's had one injected without loosing scope

  #10 opened 4 years ago by kana-ki
  1

• As a developer, I want to be able to send/receive ChronicleRecords, so I can use them with API's and Databases

  #9 opened 4 years ago by kana-ki
  0

• ChronicleRecord has NO TIMESTAMP ON IT!

  #8 opened 4 years ago by kana-ki
  0

• Refactor: Remove Chronicle record message default

  #6 opened 4 years ago by kana-ki
  0

• As a libary developer, I want ChronicleRecord to be immutable, so I can safely use them in HashSets.

  #5 opened 4 years ago by kana-ki
  0

• Add scoping to Chronicle logging

  #4 opened 4 years ago by kana-ki
  0

• Support Trace, Fatal and Emergency levels

  #2 opened 4 years ago by kana-ki
  0

• Add the ManagedThreadId on the ChronicleRecord, so it can be used in other threads

  #1 opened 4 years ago by kana-ki
  0