Skip to content
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

On app startup - Doesn't log at all when the existing file size limit has already been reached #61

Closed
ddprince17 opened this issue Oct 19, 2017 · 2 comments

Comments

@ddprince17
Copy link

Steps to reproduce:

  • PathFormat must be by {date}
  • Set fileSizeLimitBytes to let say 100000000.
  • Start the app and let it create some logs
  • Stop the app
  • Open the newly created log file and add text until it weights more than 100MB
  • Change the parameter fileSizeLimitBytes to 50000000
  • Start the app and let it log... It won't do anything

Expected behavior:

  • Since the file size limit had already been reached at the second app start, the sink should automatically create a new file names {date}_001.txt
  • The sink should respect all other options as well (like the retainedFileCountLimit)
@ddprince17
Copy link
Author

Seems like the issue will be fixed soon in the next version of the file sink.

serilog/serilog-sinks-file#35

@nblumhardt
Copy link
Member

Thanks for getting in touch @davewut - https://nblumhardt.com/2017/10/serilog-file-logging/ has some more info in case it helps 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants