Log4ALA 2.6.0

1. Optimize/fix HttpClient retry strategy to solve issue under heavy load (e.g. generate 6 million log entries within 15 minutes) which leads to duplicate log entries in Azure Log Analytics.

2. Add more detailed HTTP post debug console output (enableDebugConsoleLog=true).

3. Now the error logfile (log4ALA_error.log) contains retry log entries e.g. in case of connection issues.

4. Increase DEFAULT_HTTP_DATA_COLLECTOR_RETRY, DEFAULT_HTTP_CLIENT_TIMEOUT and DEFAULT_HTTP_CLIENT_REQUEST_TIMEOUT.

5. Decrease BATCH_SIZE_MAX quota.

6. If the logMessageToFile property is true (default false) the json request data will now be logged to the info logfile (log4ALA_info.log) again... like before version 2.5.0.

Log4ALA 2.5.0

1. Added support to passthrough the timestamp field (which will be used as Log Analytics TimeGenerated field) with the property "enablePassThroughTimeStampField"... default is false if true the field should be contained in the log message e.g with "...;DateValue=2016-05-12T20:00:00.625Z;...".
2. Replaced the complex TcpClient with the simple HttpClient.
3. Fix issue #13 "Update nuget dependencies to use Microsoft.Azure.ConfigurationManager" support
   Microsoft.Azure.ConfigurationManager as from .NET Framework 4.5.2.
4. Fix issue #14 "Azure Gov ALA workspaces not supported" now it's possible to configre the workspace domain name with the property "logAnalyticsDNS" default is "ods.opinsights.azure.com".

Log4ALA 2.4.0

Fix issue #9 "DEFAULT_MAX_FIELD_NAME_LENGTH should default to lower than 500" decrease DEFAULT_MAX_FIELD_NAME_LENGTH to 100. And fix issue with logging of formatted message strings e.g. with Log.InfoFormat("this is a {0}", "text"). Fix of issue #12 "Application Output is too chatty". Add new property disableAnonymousPropsPrefix (true/false default is false) to disable the MiscMessageFieldName (default is MiscMsg) as prefix in case of logging with anonymous types (https://github.com/ptv-logistics/Log4ALA#features under bullet point 10).

Log4ALA 2.3.6

Fix issue #8 "Problems reading settings from log4net.xml"

Log4ALA 2.3.5

Fix to remove all leading and trailing white-space characters from custom field names to avoid custom field names with e.g. leading underscores.

Log4ALA 2.3.4

Optimize json detection (now the detection will only be done if the log message really contains a json string to increase the performance by avoiding unnecessary exception flooding during the json check) and add new properties keyValueSeparator and keyValuePairSeparator to configure any other single char or multiple chars as separator for the keyValue detection in the log message (https://github.com/ptv-logistics/Log4ALA#features under bullet point 9)

Log4ALA 2.3.3

Add new property enableDebugConsoleLog to enable a kind of verbose/debug logging on console and in the log4ALA_error.log.

Log4ALA 2.3.2

Fix issue to differ get absolute path between Windows and Linux OS for reading appsettings files if running as ASP.NET Core app and removed unnecessary Console.WriteLine() output.

Log4ALA 2.3.1

Fix issue to get absolute path on linux for reading appsettings files.

Log4ALA 2.3.0

Add new property disableInfoLogFile to avoid info log file (log4ALA_info.log or defined with infoAppenderFile) on production system if true (default ist false).

AppSettings ASP.NET Core changes

• user appsetting files should be renamed from appsettings.{System.Environment.UserName.ToLower()}.json to appsettings.user_{System.Environment.UserName.ToLower()}.json
• Appsetting files which depends on a environment variable (ASPNETCORE_ENVIRONMENT, APPSETTINGS_SUFFIX) shoud be renamed from appsettings.{ASPNETCORE_ENVIRONMENT|APPSETTINGS_SUFFIX}.json to
  appsettings.env_{ASPNETCORE_ENVIRONMENT|APPSETTINGS_SUFFIX}.json