-
Notifications
You must be signed in to change notification settings - Fork 19
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
Logging to AzureBlogStorage for level Info not working #138
Comments
Try activate https://github.com/NLog/NLog/wiki/Internal-Logging and look for clues / issues. |
Thanks for the hint. Internal Log;
|
Maybe just missing flush. Ex. NLog.LogManager.Flush()
|
I flush at the end of the code. But when I flush after every log I get all messages so it seems like there is a flush issue. Any ideas on this behaviour?
When I wrap the target into an AutoFlushTargetWrapper I get all entries too. |
I'm guessing it is caused by the So when changing to a new blob-name, then it fails to wait for flush to complete for any previous-blob-names. Pull-request to improve on this are ofcourse wellcome. |
This comment was marked as outdated.
This comment was marked as outdated.
It depends on the length of the string to log. In my case the limit is exactly at 639 chars. If the message to log is 638 characters (or less), the log file will contain the message (like expected). Any ideas what could be the reason for this? |
And no errors in the NLog InternalLogger, or output when doing doing explicit flush ? |
No Errors or Warnings in the internal log file. |
I don't have any good ideas, besides using a debugger or contacting Microsoft-support. It sounds really weird with such a limit, as it would make it hard to write Json-Documents that are new-line-delimited. |
Writing logs to my Azure Blob Storage works in my first tests fine but for log level Info.
I loaded the newest version:
<PackageReference Include="NLog.Extensions.AzureBlobStorage" Version="4.2.0" />
There is just no information contained in the log for this level.
What's wrong?
`
string blobName = $"{this.AzureStorageBlobNamePrefix}${{shortdate}}${{level}}.log";
The text was updated successfully, but these errors were encountered: