You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thanks for an awesome package. Request to make a PR / feature change.
We are logging with Serilog via a common adapter to loki.. With CompactJsonFormatter and RenderedCompactJsonFormatter as the formatter.
We would like veryt much that information level is always added to the message. and we can rename the default @fields to specific values. Yes, we can use the ExpressionTemplate formatted also. But this does not include the convenient logic included in the CompactJsonFormatter and RenderedCompactJsonFormatter.
Can I make a PR to add options to the ctor for CompactJsonFormatter and RenderedCompactJsonFormatter? Then ppl can control some behaviour, but keep the default as is?
The text was updated successfully, but these errors were encountered:
Hi! Thanks for the extra info. This really seems like a configuration management problem - deploying new logger configuration to 100 microservices is going to need some supporting infrastructure.
Closing as a duplicate of #20, but if you need any help with getting ExpressionTemplate (or a copy of CompactJsonFormatter) set up to your liking, please let me know. Thanks!
Hi, thanks for an awesome package. Request to make a PR / feature change.
We are logging with Serilog via a common adapter to loki.. With CompactJsonFormatter and RenderedCompactJsonFormatter as the formatter.
We would like veryt much that information level is always added to the message. and we can rename the default @fields to specific values. Yes, we can use the ExpressionTemplate formatted also. But this does not include the convenient logic included in the CompactJsonFormatter and RenderedCompactJsonFormatter.
Can I make a PR to add options to the ctor for CompactJsonFormatter and RenderedCompactJsonFormatter? Then ppl can control some behaviour, but keep the default as is?
The text was updated successfully, but these errors were encountered: