We Keep Coding

How can I log into a text file(not xml) on my Azure BlobStorage using log4net?

So I'm already logging (log4net) on my own machine using the following configuration
<appender name="LogFileAppender" type="log4net.Appender.RollingFileAppender">
<param name="File" value="mylog.txt" />
<param name="AppendToFile" value="true" />
<rollingStyle value="Size" />
<maxSizeRollBackups value="10" />
<maximumFileSize value="5MB" />
<staticLogFileName value="true" />
<layout type="log4net.Layout.PatternLayout">
<param name="ConversionPattern" value="%date [%thread] %-5level %logger [%M %C] - %message%newline" />
</layout>
</appender>
Just to test log4net and make sure everything is working, now I want to log on my Azure blob storage, I'm using log4net.Appender.Azure nuget package and it did log to my blob storage using this configuration:
<appender name="AzureBlobAppender" type="log4net.Appender.AzureBlobAppender, log4net.Appender.Azure">
<param name="ContainerName" value="testblob" />
<param name="DirectoryName" value="logs/" />
<!-- You can either specify a connection string or use the ConnectionStringName property instead -->
<param name="ConnectionString" value="UseDevelopmentStorage=true;" />
<!--<param name="ConnectionStringName" value="GlobalConfigurationString" />-->
<bufferSize value="5" />
</appender>
But this configuration left me with many XML files instead of ONE text file so is there a way to do that? I searched around but found nothing related to this.
EDIT: So to append the xml into only one can be done using the following configuration
<appender name="AzureAppendBlobAppender" type="log4net.Appender.AzureAppendBlobAppender, log4net.Appender.Azure">
<param name="ContainerName" value="testloggingblob"/>
<param name="DirectoryName" value="logs"/>
<!-- You can either specify a connection string or use the ConnectionStringName property instead -->
<param name="ConnectionString" value="UseDevelopmentStorage=true"/>
<!--<param name="ConnectionStringName" value="GlobalConfigurationString" />-->
</appender>
But this did not work for me because im using the Azure Storage Emulator and the Append Blob operations are not supported by the emulator currently.
Still no idea how to go from XML to text file.

use AzureAppendBlobAppender will log into one file per day, but still inside the file it's all XML entries.
If you want to use the layout option, clone the source code from that link and change the source code of AzureAppendBlobAppender and build your own appender
private void ProcessEvent(LoggingEvent loggingEvent)
{
CloudAppendBlob appendBlob = _cloudBlobContainer.GetAppendBlobReference(Filename(_directoryName));
string content;
try
{
content = _lineFeed + RenderLoggingEvent(loggingEvent);
}catch(InvalidOperationException e)
{
//if no layout set, using xml
content = _lineFeed + loggingEvent.GetXmlString(Layout);
}
using (MemoryStream ms = new MemoryStream(Encoding.UTF8.GetBytes(content)))
{
appendBlob.AppendBlock(ms);
}
}
Then you will be able to use your layout config inside of appender
<layout type="log4net.Layout.PatternLayout">
<param name="ConversionPattern" value="%date [%thread] %-5level %logger [%M %C] - %message%newline" />
</layout>

First of all, try to convert the XML file to a txt file using the following blog tutorial
Then you could use other features rather than log4net if you want to append to textfile. the blobAppend functionality to append to a log file (text file as you require):
Your first take is use: BlobAppend and user SAS URI a sample looks as this:
CloudAppendBlob appendBlob = new CloudAppendBlob(new Uri("https://{storage_account}.blob.core.windows.net/{your_container}/append-blob.log?st=2017-09-25T02%3A10%3A00Z&se=2017-09-27T02%3A10%3A00Z&sp=rwl&sv=2015-04-05&sr=b&sig=d0MENO44GjtBLf7L8U%2B%2F2nGwPAayjiVSSHaKJgEkmIs%3D"));
appendBlob.AppendFromFile("{filepath}\source.txt");
Second:
I'd recommend checking this specific tutorial that is external, providing and example of blobAppend: https://dzone.com/articles/adding-to-an-existing-azure-blob
These should you get to the results you wish.

log4net multiple loggers - properties

log4net v. 2.0.8
I've got some problems in multiple logging with log4net. I'm developing an application that works with n devices and I would like to have a single log file for each device.
log4net.config
<log4net>
<appender name="LogFileAppender" type="log4net.Appender.RollingFileAppender">
<file type="log4net.Util.PatternString" value="%envFolderPath{LocalApplicationData}/Foo/Device%property{DeviceID}/log.txt"/>
<appendToFile value="true"/>
<maxSizeRollBackups value="10"/>
<maximumFileSize value="10MB"/>
<layout type="log4net.Layout.PatternLayout">
<param name="Header" value="BEGIN LOGGING AT %date *** %property *** %newline" type="log4net.Util.PatternString" />
<param name="Footer" value="END LOGGING AT %date *** %property *** %newline" type="log4net.Util.PatternString" />
<param name="ConversionPattern" value="%date [%thread] %-5level %-5class{1} %-5method(%line) %message %newline" />
</layout>
<filter type="log4net.Filter.PropertyFilter">
<key value="Version" />
<stringToMatch value="1" />
</filter>
</appender>
<root>
<level value="ALL" />
<appender-ref ref="LogFileAppender" />
</root>
and this is the code
public DeviceClass(string deviceID)
{
InitializeComponent();
GlobalContext.Properties["DeviceID"] = deviceID;
logger = LogManager.GetLogger(System.Reflection.MethodBase.GetCurrentMethod().DeclaringType);
logger.Debug("Hello world");
The problem is that if I have for example two devices I got just the first log file with the messages from all devices.

I'm not a Log4Net expert, but I believe that the log manager is going to initialize the logger and all of its appenders the first time that you call GetLogger for the given type/name (type under covers is translated to a string name). That being the case, it wouldn't re-initialize one per device. My suggestion for you is to try creating a composite of the type name and device ID using something like:
logger = LogManager.GetLogger($"{System.Reflection.MethodBase.GetCurrentMethod().DeclaringType.FullName}{deviceId}");

Log4Net - Log to Azure Blob Storage doesn't create logs

I'm trying to log information to Azure Blob Storage using this Nuget libraries:
log4net (2.0.3)
log4net.Appender.Azure (1.3.0.19665)
My app.config file contains:
<configuration>
<configSections>
<section type="log4net.Config.Log4NetConfigurationSectionHandler, log4net" name="log4net" />
</configSections>
<connectionStrings>
<add name="StorageConnectionString" connectionString="!##$%^&*()" />
</connectionStrings>
...
<log4net>
<appender name="AzureBlobAppender" type="log4net.Appender.AzureBlobAppender, log4net.Appender.Azure">
<param name="ContainerName" value="Logs"/>
<param name="DirectoryName" value="logs"/>
<param name="ConnectionStringName" value="StorageConnectionString" />
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%date [%thread] %-5level %logger - %message%newline"/>
</layout>
</appender>
<root>
<level value="ALL" />
<appender-ref ref="AzureBlobAppender" />
</root>
Appender creates storage container but it's always empty. What am I doing wrong?

If you are currently doing development on development PC, better use the cloud emulator by inserting this line as your connection string
<param name="ConnectionString" value="UseDevelopmentStorage=true" />
If you are currently testing directly into the cloud, you can put the connection string which you can get in your azure portal.

how to create dynamic log using log4net

My Project is in C# (Windows Form) .net3.5
In my code there are multiple events and in each event multiple searches are running.
I have to create log file for each event and multiple searches can access & write this single log file.
The problem is that I don't know how to use log4net for creating multiple logs with dynamic(set at run time) names.
How to set there location(Path)
I explorer internet regarding my problem but haven't found any help which address this type of issues.
any idea pls

log4net is generally used to have mutiple sources and appenders.
To generate a defined source, ask LogManager to have a named log, generally we use a type to identify a log, but feel free to use a string if you want:
var myLog = LogManager.GetLogger("NAME");
....
var myLog = LogManager.GetLogger(GetType());
In the first case logger is identified by "NAME", in the second by the type name with namespaces.
Then you can configure the appenders, for all logs, for a subset of them, with filters and so on.
Let's see an example:
<configuration>
<configSections>
<section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler, log4net"/>
</configSections>
<log4net>
<appender name="MYFILE" type="log4net.Appender.RollingFileAppender">
<file value=".\logs\myname.log"/>
<appendToFile value="true"/>
<rollingStyle value="Size"/>
<maxSizeRollBackups value="10"/>
<maximumFileSize value="10MB"/>
<staticLogFileName value="true"/>
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%date %-5level (%thread) %logger - %message%newline"/>
</layout>
</appender>
<root>
<level value="INFO"/>
<!-- all logger append to these appenders />
<appender-ref ref="xxxxxx"/>
</root>
<logger name="NAME">
<level value="INFO"/>
<appender-ref ref="MYFILE"/>
</logger>
<!-- add other appender here -->
Don't forget to call at your application start XmlConfigurator.Configure();

Can't get Log4Net to work in our WCF application [duplicate]

This question already has answers here:
Log4Net in WCF not working
(6 answers)
Closed 9 years ago.
We are trying to use Log4Net to log from our IIS 6-deployed WCF Application. We are trying to log to a file, but can't seem to get the log files to be created, let alone see the logging output in them. The pertinent pieces of out web.config are:
<sectionGroup name="common">
<section name="logging" type="Common.Logging.ConfigurationSectionHandler, Common.Logging" />
</sectionGroup>
...
<common>
<logging>
<factoryAdapter type="Common.Logging.Simple.TraceLoggerFactoryAdapter, Common.Logging">
<arg key="level" value="INFO" />
<arg key="showLogName" value="true" />
<arg key="showDataTime" value="true" />
<arg key="dateTimeFormat" value="yyyy/MM/dd HH:mm:ss:fff" />
</factoryAdapter>
</logging>
</common>
<log4net>
<appender name="FileAppender" type="log4net.Appender.RollingFileAppender">
<param name="File" value="c:\logs\ApplicationInfoTest.log" />
<threshold value="INFO" />
<param name="AppendToFile" value="true" />
<param name="DatePattern" value="ddMMyyyy" />
<param name="MaxSizeRollBackups" value="10" />
<param name="MaximumFileSize" value="10MB" />
<param name="RollingStyle" value="Size" />
<param name="StaticLogFileName" value="true" />
<layout type="log4net.Layout.PatternLayout">
<param name="Header" value="\r\n\r\n---------------------------------------------\r\n" />
<param name="Footer" value="\r\n---------------------------------------------\r\n\r\n" />
<param name="ConversionPattern" value="%d [%t] %-5p - %m%n" />
</layout>
</appender>
<root>
<level value="INFO" />
<appender-ref ref="FileAppender" />
</root>
</log4net>
With this configuration we can see INFO level logging coming out of our application when using DebugView, but it is clear that this is from the
piece and not the
piece.
Is there something that we have failed to set up in web.config? Is it a permissions issue with the directory we have created for the logs to be written to?
Please point out our obvious mistake.

I have also had to add this line to the AssemblyInfo.cs file of my application in order to get log4net working.
// LOG 4 net config
[assembly:log4net.Config.XmlConfigurator(Watch=true)]

Use ProcessMonitor from SysInternals to find out where permissions are being refused
(Potentially you can determine the same info by attaching a debugger and trapping on exceptions, not in Just My Code)
Are you sure that the process under which the service is running has permissions on the folder you're trying to write to?

Try XmlConfigurator.Configure()

Do you have a configuration section configured for log4net? I didn't see that in your code snippet

I would first run the WCF service as a console application - this way you can specify the user account for the application to run as and see if the problem is with your config or with a permissions issue running the service through IIS.
If you are unsure of how to run the service as a console application take a look at http://www.jacopretorius.net/2009/08/running-windows-service-inside-console.html