-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XML configuration support #25
Comments
Hi! There's no work-in-progress on this; the main issue is that we haven't come up with a syntax that we like - suggestions for how this would look are welcome. Thanks! |
this would look great for me:
|
Thanks for the suggestion 👍 |
Any further update on if/when this would be available for use? |
Here's a slight tweak: <!-- No need to nest the `using` directive for `File` -->
<add key="serilog:using:Async" value="Serilog.Sinks.Async" />
<add key="serilog:using:File" value="Serilog.Sinks.File" />
<add key="serilog:write-to:Async.bufferSize" value="1000" />
<!-- Configure is an `Action<LoggerSinkConfiguration>`; this is what `write-to` effectively
applies to, so by including the parameter name and dropping back into sink configuration
is a mechanism we could carry through to other `Action<T>` arguments -->
<add key="serilog:write-to:Async.configure:File.path" value="..." />
<add key="serilog:write-to:Async.configure:File.rollOnFileSizeLimit" value="true" />
<add key="serilog:write-to:Async.configure:File.rollingInterval" value="Day" />
... Trying to take a more regular approach to how parameters are matched/provided will make it easier to add reliable support to Serilog Analyzer. The next step for this one is to create an issue in serilog/serilog, where the code for this feature would live. If there's support, and someone is able to send a strong PR, I don't think anything would prevent this going into a 2.6.1. |
We're now tracking this in: serilog/serilog#1072 |
@nblumhardt |
Hi @mishrapw - no, the issue linked in my comment one above yours is tracking progress. Cheers! |
Is there a plan for this feature?
The text was updated successfully, but these errors were encountered: