diff --git a/NLog.xsd b/NLog.xsd index 075bb91..cf06a05 100644 --- a/NLog.xsd +++ b/NLog.xsd @@ -37,12 +37,12 @@ - Global log level threshold for application log messages. Messages below this level won't be logged.. + Global log level threshold for application log messages. Messages below this level won't be logged. - Throw an exception when there is an internal error. Default value is: false. + Throw an exception when there is an internal error. Default value is: false. Not recommend to set to true in production! @@ -72,7 +72,7 @@ - Perform mesage template parsing and formatting of LogEvent messages (true = Always, false = Never, empty = Auto Detect). Default value is: empty. + Perform message template parsing and formatting of LogEvent messages (true = Always, false = Never, empty = Auto Detect). Default value is: empty. @@ -123,7 +123,7 @@ - Name of the logger. May include '*' character which acts like a wildcard. Allowed forms are: *, Name, *Name, Name* and *Name* + Filter on the name of the logger. May include wildcard characters ('*' or '?'). @@ -158,7 +158,17 @@ - Enable or disable logging rule. Disabled rules are ignored. + Enable this rule. Note: disabled rules aren't available from the API. + + + + + Rule identifier to allow rule lookup with Configuration.FindRuleByName and Configuration.RemoveRuleByName. + + + + + Loggers matching will be restricted to specified minimum level for following rules. @@ -171,6 +181,11 @@ + + + Default action if none of the filters match. + + @@ -210,12 +225,19 @@ + + + + Variable value. Note, the 'value' attribute has precedence over this one. + + + Variable name. - + Variable value. @@ -274,47 +296,53 @@ - - - - - - - + + + + + + + + Name of the target. - + - Number of log events that should be processed in a batch by the lazy writer thread. + Action to be taken when the lazy writer thread request queue count exceeds the set limit. - + - Limit of full s to write before yielding into Performance is better when writing many small batches, than writing a single large batch + Limit on the number of requests in the lazy writer thread request queue. - + - Action to be taken when the lazy writer thread request queue count exceeds the set limit. + Number of log events that should be processed in a batch by the lazy writer thread. - + - Limit on the number of requests in the lazy writer thread request queue. + Whether to use the locking queue, instead of a lock-free concurrent queue The locking queue is less concurrent when many logger threads, but reduces memory allocation + + + + + Limit of full s to write before yielding into Performance is better when writing many small batches, than writing a single large batch - Time in milliseconds to sleep between batches. + Time in milliseconds to sleep between batches. (1 or less means trigger on new activity) - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -331,11 +359,17 @@ - - - - + + + + + + + + Name of the target. + + Delay the flush until the LogEvent has been confirmed as written @@ -346,14 +380,14 @@ Condition expression. Log events who meet this condition will cause a flush on the wrapped target. - + - Name of the target. + Only flush when LogEvent matches condition. Ignore explicit-flush, config-reload-flush and shutdown-flush - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -363,31 +397,31 @@ - - - - - - + + + + + + Name of the target. - + Number of log events to be buffered. - + - Timeout (in milliseconds) after which the contents of buffer will be flushed if there's no write in the specified period of time. Use -1 to disable timed flushes. + Action to take if the buffer overflows. - + - Action to take if the buffer overflows. + Timeout (in milliseconds) after which the contents of buffer will be flushed if there's no write in the specified period of time. Use -1 to disable timed flushes. @@ -395,9 +429,9 @@ Indicates whether to use sliding timeout. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -413,162 +447,186 @@ - - - - - - - - - - - - - + + - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + Name of the target. - + - Encoding to be used. + Separator for operation-states-stack. - + - Instance of that is used to format log messages. + Stack separator for log4j:NDC in output from nested context. - + - End of line value if a newline is appended at the end of log message . + Renderer for log4j:event logger-xml-attribute (Default ${logger}) - + - Maximum message size in bytes. + Whether to include the contents of the properties-dictionary. - + - Indicates whether to append newline at the end of log message. + Whether to include log4j:NDC in output from nested context. - + - Action that should be taken if the will be more connections than . + Indicates whether to include source info (file name and line number) in the information sent over the network. - + - Maximum queue size. + Whether to include log4j:NDC in output from nested context. - + - Maximum current connections. 0 = no maximum. + Option to include all properties from the log events - + - Indicates whether to keep connection open whenever possible. + Indicates whether to include call site (class and method name) in the information sent over the network. - + - Size of the connection cache (number of connections which are kept alive). + AppInfo field. By default it's the friendly name of the current AppDomain. - + - Network address. + Instance of that is used to format log messages. + + + + + Indicates whether to include NLog-specific extensions to log4j schema. + + + + + Action that should be taken, when more connections than . + + + + + Get or set the SSL/TLS protocols. Default no SSL/TLS is used. Currently only implemented for TCP. + + + + + Action that should be taken, when more pending messages than . - Action that should be taken if the message is larger than maxMessageSize. + Action that should be taken if the message is larger than - + - NDLC item separator. + Maximum queue size for a single connection. Requires = true - + - NDC item separator. + Size of the connection cache (number of connections which are kept alive). Requires = true - + - Indicates whether to include NLog-specific extensions to log4j schema. + Indicates whether to keep connection open whenever possible. - + - Indicates whether to include source info (file name and line number) in the information sent over the network. + The number of seconds a connection will remain idle before the first keep-alive probe is sent - + - Indicates whether to include contents of the stack. + Network address. - + - Indicates whether to include stack contents. + Maximum simultaneous connections. Requires = false - + - Indicates whether to include dictionary contents. + Type of compression for protocol payload. Useful for UDP where datagram max-size is 8192 bytes. - + - Indicates whether to include dictionary contents. + Skip compression when protocol payload is below limit to reduce overhead in cpu-usage and additional headers - + - Indicates whether to include call site (class and method name) in the information sent over the network. + Indicates whether to append newline at the end of log message. - + - Option to include all properties from the log events + Encoding to be used. - + - AppInfo field. By default it's the friendly name of the current AppDomain. + End of line value if a newline is appended at the end of log message . - + - Renderer for log4j:event logger-xml-attribute (Default ${logger}) + Maximum message size in bytes. On limit breach then action is activated. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -576,11 +634,32 @@ + + + + + + + + + + + + + + + + + + + + + @@ -588,19 +667,32 @@ + + + + + + + - - + + + + + + Viewer parameter name. + + - Layout that should be use to calcuate the value for the parameter. + Layout that should be use to calculate the value for the parameter. - + - Viewer parameter name. + Whether an attribute with empty value should be included in the output @@ -608,17 +700,20 @@ - - - - - - - - + + + + + + + + + + + - + @@ -645,14 +740,29 @@ Indicates whether to auto-check if the console is available. - Disables console writing if Environment.UserInteractive = False (Windows Service) - Disables console writing if Console Standard Input is not available (Non-Console-App) + + + Enables output using ANSI Color Codes + + The encoding for writing messages to the . - + - Indicates whether the error stream (stderr) should be used instead of the output stream (stdout). + Indicates whether to send the log messages to the standard error instead of the standard output. + + + + + Indicates whether to auto-flush after + + + + + Indicates whether to auto-check if the console has been redirected to file - Disables coloring logic when System.Console.IsOutputRedirected = true @@ -660,9 +770,9 @@ Indicates whether to use default row highlighting rules. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -691,18 +801,18 @@ - - - + + + - + - Condition that must be met in order to set the specified foreground and background color. + Background color. - + - Background color. + Condition that must be met in order to set the specified foreground and background color. @@ -713,19 +823,35 @@ - - - - - - - + + + + + + + + + + + Background color. + + Compile the ? This can improve the performance, but at the costs of more memory usage. If false, the Regex Cache is used. + + + Condition that must be met before scanning the row for highlight of words + + + + + Foreground color. + + Indicates whether to ignore case when comparing texts. @@ -746,29 +872,21 @@ Indicates whether to match whole words only. - - - Background color. - - - - - Foreground color. - - - - - - - - - - + + + + + + + + + + @@ -790,6 +908,11 @@ Footer. + + + Indicates whether to auto-flush after + + Indicates whether to auto-check if the console is available - Disables console writing if Environment.UserInteractive = False (Windows Service) - Disables console writing if Console Standard Input is not available (Non-Console-App) @@ -800,243 +923,121 @@ The encoding for writing messages to the . - + Indicates whether to send the log messages to the standard error instead of the standard output. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + Whether to activate internal buffering to allow batch writing, instead of using + + + + + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. - + - - - - - - - - - - - - - - - - - + + + + + Name of the target. - - - Obsolete - value will be ignored! The logging code always runs outside of transaction. Gets or sets a value indicating whether to use database transactions. Some data providers require this. - - - + - Database user name. If the ConnectionString is not provided this value will be used to construct the "User ID=" part of the connection string. + Text to be rendered. - + - Name of the database provider. + Header. - + - Database password. If the ConnectionString is not provided this value will be used to construct the "Password=" part of the connection string. + Footer. - + - Indicates whether to keep the database connection open between the log events. + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. - + + + + + + + + + + + + + + - Database name. If the ConnectionString is not provided this value will be used to construct the "Database=" part of the connection string. + Name of the target. - + - Name of the connection string (as specified in <connectionStrings> configuration section. + Text to be rendered. - + - Connection string. When provided, it overrides the values specified in DBHost, DBUserName, DBPassword, DBDatabase. + Header. - + - Database host name. If the ConnectionString is not provided this value will be used to construct the "Server=" part of the connection string. + Footer. - + - Connection string using for installation and uninstallation. If not provided, regular ConnectionString is being used. + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. - + + + + + + + + + + + + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + Name of the target. - + - Text of the SQL command to be run on each log level. + Layout used to format log messages. - + - Type of the SQL command to be run on each log level. - - - - - - - - - - - - - - - - - - - - - - - Type of the command. - - - - - Connection string to run the command against. If not provided, connection string from the target is used. - - - - - Indicates whether to ignore failures. - - - - - Command text. - - - - - - - - - - - - - - Layout that should be use to calcuate the value for the parameter. - - - - - Database parameter name. - - - - - Database parameter precision. - - - - - Database parameter scale. - - - - - Database parameter size. - - - - - - - - - - - - - - - - Name of the target. - - - - - Text to be rendered. - - - - - Header. - - - - - Footer. - - - - - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit - - - - - - - - - - - - - - - - Name of the target. - - - - - Layout used to format log messages. - - - - - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -1046,18 +1047,18 @@ - - - - - - - - - - - - + + + + + + + + + + + + @@ -1076,7 +1077,7 @@ - Optional entrytype. When not set, or when not convertable to then determined by + Optional entry type. When not set, or when not convertible to then determined by @@ -1096,7 +1097,7 @@ - Maximum Event log size in kilobytes. If null, the value won't be set. Default is 512 Kilobytes as specified by Eventlog API + Maximum Event log size in kilobytes. @@ -1114,9 +1115,9 @@ Action to take if the message is larger than the option. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -1133,9 +1134,10 @@ - - - + + + + @@ -1147,9 +1149,14 @@ Indicates whether to return to the first target after any successful write. - + + + Whether to enable batching, but fallback will be handled individually + + + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -1159,52 +1166,58 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Name of the target. + + + Name of the file to write to. + + Text to be rendered. @@ -1220,24 +1233,34 @@ Footer. - + - File encoding. + Indicates whether the footer should be written only when the file is archived. - + - Line ending mode. + Maximum number of archive files that should be kept. - + - Indicates whether to compress archive files into the zip archive format. + Maximum days of archive files that should be kept. - + - Way file archives are numbered. + Value of the file size threshold to archive old log file on startup. + + + + + Indicates whether to archive old log file on startup. + + + + + Indicates whether to compress archive files into the zip archive format. @@ -1255,29 +1278,29 @@ Indicates whether to automatically archive log files every time the specified time passes. - + - Size in bytes above which log files will be automatically archived. Warning: combining this with isn't supported. We cannot create multiple archive files, if they should have the same name. Choose: + Value specifying the date format to use when archiving files. - + - Maximum number of archive files that should be kept. + Size in bytes above which log files will be automatically archived. - + - Indicates whether the footer should be written only when the file is archived. + Way file archives are numbered. - + - Maximum number of log filenames that should be stored as existing. + Indicates whether to create directories if they do not exist. - + - Is the an absolute or relative path? + Indicates whether file creation calls should be synchronized by a system global mutex. @@ -1285,19 +1308,24 @@ Gets or set a value indicating whether a managed file stream is forced, instead of using the native implementation. - + - Value indicationg whether file creation calls should be synchronized by a system global mutex. + Is the an absolute or relative path? - + - Indicates whether to replace file contents on each write instead of appending log message at the end. + File attributes (Windows only). + + + + + Cleanup invalid values in a filename, e.g. slashes in a filename. If set to true, this can impact the performance of massive writes. If set to false, nothing gets written when the filename is wrong. - Indicates whether to write BOM (byte order mark) in created files + Indicates whether to write BOM (byte order mark) in created files. Defaults to true for UTF-16 and UTF-32 @@ -1305,44 +1333,44 @@ Indicates whether to enable log file(s) to be deleted. - + - Name of the file to write to. + Indicates whether to delete old log file on startup. - + - Value specifying the date format to use when archiving files. + File encoding. - + - Indicates whether to archive old log file on startup. + Indicates whether to replace file contents on each write instead of appending log message at the end. - + - Cleanup invalid values in a filename, e.g. slashes in a filename. If set to true, this can impact the performance of massive writes. If set to false, nothing gets written when the filename is wrong. + Line ending mode. - + - Indicates whether to create directories if they do not exist. + Whether or not this target should just discard all data that its asked to write. Mostly used for when testing NLog Stack except final write - + - Indicates whether to delete old log file on startup. + Delay in milliseconds to wait before attempting to write to the file again. - + - File attributes (Windows only). + Maximum number of seconds before open files are flushed. Zero or negative means disabled. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + Maximum number of seconds that files are kept open. Zero or negative means disabled. @@ -1350,9 +1378,14 @@ Indicates whether concurrent writes to the log file by multiple processes on different network hosts. - + + + Log file buffer size in bytes. + + + - Maximum number of seconds that files are kept open. If this number is negative the files are not automatically closed after a period of inactivity. + Indicates whether to automatically flush the file buffers after each log message. @@ -1365,11 +1398,6 @@ Indicates whether to keep log file open instead of opening and closing it on each logging event. - - - Whether or not this target should just discard all data that its asked to write. Mostly used for when testing NLog Stack except final write - - Indicates whether concurrent writes to the log file by multiple processes on the same host. @@ -1380,37 +1408,14 @@ Number of times the write is appended on the file before NLog discards the log message. - - - Delay in milliseconds to wait before attempting to write to the file again. - - - - - Log file buffer size in bytes. - - - - - Maximum number of seconds before open files are flushed. If this number is negative or zero the files are not flushed by timer. - - - + - Indicates whether to automatically flush the file buffers after each log message. + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. - - - - - - - - @@ -1435,6 +1440,14 @@ + + + + + + + + @@ -1459,9 +1472,10 @@ - - - + + + + @@ -1473,285 +1487,141 @@ Condition expression. Log events who meet this condition will be forwarded to the wrapped target. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. - + - - - - - - - - - + + + Name of the target. - - - Windows domain name to change context to. - - - - - Required impersonation level. - - - - - Type of the logon provider. - - - - - Logon Type. - - - - - User account password. - - - + - Indicates whether to revert to the credentials of the process instead of impersonating another user. + Identifier to perform group-by - + - Username to change context to. - - - - - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + - + - Interval in which messages will be written up to the number of messages. + Name of the target. - + - Maximum allowed number of messages written per . + Interval in which messages will be written up to the number of messages. - + - Name of the target. + Maximum allowed number of messages written per . - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. - + - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + Name of the target. - + - Endpoint address. + Text to be rendered. - + - Name of the endpoint configuration in WCF configuration file. + Header. - + - Indicates whether to use a WCF service contract that is one way (fire and forget) or two way (request-reply) + Footer. - + - Client ID. + Indicates whether NewLine characters in the body should be replaced with tags. - + - Indicates whether to include per-event properties in the payload sent to the server. + Priority used for sending mails. - + - Indicates whether to use binary message encoding. + Encoding to be used for sending e-mail. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit - - - - - - - - - - - - - - - Layout that should be use to calculate the value for the parameter. - - - - - Name of the parameter. - - - - - Type of the parameter. - - - - - Type of the parameter. Obsolete alias for - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Name of the target. - - - - - Text to be rendered. - - - - - Header. - - - - - Footer. - - - - - Indicates whether NewLine characters in the body should be replaced with tags. - - - - - Priority used for sending mails. - - - - - Encoding to be used for sending e-mail. - - - - - BCC email addresses separated by semicolons (e.g. john@domain.com;jane@domain.com). + BCC email addresses separated by semicolons (e.g. john@domain.com;jane@domain.com). @@ -1789,12 +1659,12 @@ Recipients' email addresses separated by semicolons (e.g. john@domain.com;jane@domain.com). - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. - + Indicates the SMTP client timeout. @@ -1824,7 +1694,7 @@ Indicates whether SSL (secure sockets layer) should be used when communicating with SMTP server. - + Port number that SMTP Server is listening on. @@ -1834,7 +1704,7 @@ Indicates whether the default Settings from System.Net.MailSettings should be used. - + Folder where applications save mail messages to be processed by the local SMTP server. @@ -1865,9 +1735,12 @@ - - - + + + + + + @@ -1876,12 +1749,27 @@ - Layout used to format log messages. + Text to be rendered. + + + + + Header. + + + + + Footer. + + + + + Max number of items to have in memory - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -1891,11 +1779,11 @@ - - - + - + + + @@ -1912,32 +1800,65 @@ Method name. The method must be public and static. Use the AssemblyQualifiedName , https://msdn.microsoft.com/en-us/library/system.type.assemblyqualifiedname(v=vs.110).aspx e.g. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. + + + + + + + + + + Name of the parameter. + + + + + Layout that should be use to calculate the value for the parameter. + + + + + Fallback value when result value is not available + + + + + Type of the parameter. + + + - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + @@ -1949,64 +1870,89 @@ Layout used to format log messages. - + - Encoding to be used. + Get or set the SSL/TLS protocols. Default no SSL/TLS is used. Currently only implemented for TCP. - + - End of line value if a newline is appended at the end of log message . + Action that should be taken, when more pending messages than . - + - Maximum message size in bytes. + Action that should be taken, when more connections than . - + - Indicates whether to append newline at the end of log message. + Maximum queue size for a single connection. Requires = true - + - Network address. + Action that should be taken if the message is larger than + + + + + Indicates whether to keep connection open whenever possible. + + + + + The number of seconds a connection will remain idle before the first keep-alive probe is sent - Size of the connection cache (number of connections which are kept alive). + Size of the connection cache (number of connections which are kept alive). Requires = true - + - Indicates whether to keep connection open whenever possible. + Network address. - Maximum current connections. 0 = no maximum. + Maximum simultaneous connections. Requires = false - + - Maximum queue size. + Type of compression for protocol payload. Useful for UDP where datagram max-size is 8192 bytes. - + - Action that should be taken if the will be more connections than . + Skip compression when protocol payload is below limit to reduce overhead in cpu-usage and additional headers - + + + Indicates whether to append newline at the end of log message. + + + + + Encoding to be used. + + + - Action that should be taken if the message is larger than maxMessageSize. + End of line value if a newline is appended at the end of log message . + + + + + Maximum message size in bytes. On limit breach then action is activated. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -2016,107 +1962,96 @@ - - - - - - - - - - - - - + + - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + Name of the target. - - - Encoding to be used. - - - - - Instance of that is used to format log messages. - - - - - End of line value if a newline is appended at the end of log message . - - - + - Maximum message size in bytes. + Separator for operation-states-stack. - + - Indicates whether to append newline at the end of log message. + Stack separator for log4j:NDC in output from nested context. - + - Action that should be taken if the will be more connections than . + Renderer for log4j:event logger-xml-attribute (Default ${logger}) - + - Maximum queue size. + Whether to include the contents of the properties-dictionary. - + - Maximum current connections. 0 = no maximum. + Whether to include log4j:NDC in output from nested context. - + - Indicates whether to keep connection open whenever possible. + Indicates whether to include source info (file name and line number) in the information sent over the network. - + - Size of the connection cache (number of connections which are kept alive). + Whether to include log4j:NDC in output from nested context. - + - Network address. + Option to include all properties from the log events - + - Action that should be taken if the message is larger than maxMessageSize. + Indicates whether to include call site (class and method name) in the information sent over the network. - + - NDLC item separator. + AppInfo field. By default it's the friendly name of the current AppDomain. - + - NDC item separator. + Instance of that is used to format log messages. @@ -2124,219 +2059,134 @@ Indicates whether to include NLog-specific extensions to log4j schema. - + - Indicates whether to include source info (file name and line number) in the information sent over the network. + Action that should be taken, when more connections than . - + - Indicates whether to include contents of the stack. + Get or set the SSL/TLS protocols. Default no SSL/TLS is used. Currently only implemented for TCP. - + - Indicates whether to include stack contents. + Action that should be taken, when more pending messages than . - + - Indicates whether to include dictionary contents. + Action that should be taken if the message is larger than - + - Indicates whether to include dictionary contents. + Maximum queue size for a single connection. Requires = true - + - Indicates whether to include call site (class and method name) in the information sent over the network. + Size of the connection cache (number of connections which are kept alive). Requires = true - + - Option to include all properties from the log events + Indicates whether to keep connection open whenever possible. - + - AppInfo field. By default it's the friendly name of the current AppDomain. + The number of seconds a connection will remain idle before the first keep-alive probe is sent - + - Renderer for log4j:event logger-xml-attribute (Default ${logger}) + Network address. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + Maximum simultaneous connections. Requires = false - - - - - - - - - - - - - + - Name of the target. + Type of compression for protocol payload. Useful for UDP where datagram max-size is 8192 bytes. - + - Layout used to format log messages. + Skip compression when protocol payload is below limit to reduce overhead in cpu-usage and additional headers - + - Indicates whether to perform layout calculation. + Indicates whether to append newline at the end of log message. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + Encoding to be used. - - - - - - - - - - - - + - Name of the target. + End of line value if a newline is appended at the end of log message . - + - Layout used to format log messages. + Maximum message size in bytes. On limit breach then action is activated. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. - + - - - - - - - - - + + + + Name of the target. - - - Indicates whether performance counter should be automatically created. - - - - - Name of the performance counter category. - - - - - Counter help text. - - - - - Name of the performance counter. - - - - - Performance counter type. - - - + - The value by which to increment the counter. + Layout used to format log messages. - + - Performance counter instance name. + Indicates whether to perform layout calculation. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + - + @@ -2348,9 +2198,9 @@ Default filter to be applied when no specific rule matches. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -2358,8 +2208,8 @@ - - + + @@ -2376,17 +2226,17 @@ - - + + Name of the target. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -2396,18 +2246,18 @@ - - - + + + Name of the target. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -2422,27 +2272,33 @@ - - - - + + + + + Name of the target. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. - + - Number of retries that should be attempted on the wrapped target in case of a failure. + Whether to enable batching, and only apply single delay when a whole batch fails - + + + Number of retries that should be attempted on the wrapped target in case of a failure. + + + Time to wait between retries in milliseconds. @@ -2454,17 +2310,17 @@ - - + + Name of the target. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -2474,17 +2330,17 @@ - - + + Name of the target. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -2494,10 +2350,13 @@ - - - - + + + + + + + @@ -2506,17 +2365,32 @@ - Layout used to format log messages. + Text to be rendered. + + + + + Header. + + + + + Footer. + + + + + Forward to (Instead of ) - Always use independent of + Force use independent of - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -2526,32 +2400,33 @@ - + - - - - - - - - - - - - - + - + + + + + + + + + + + + + + Name of the target. - + - Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + NLog Layout are by default threadsafe, so multiple threads can be rendering logevents at the same time. This ensure high concurrency with no lock-congestion for the application-threads, especially when using or AsyncTaskTarget. But if using custom or that are not threadsafe, then this option can enabled to protect against thread-concurrency-issues. Allowing one to update to NLog 5.0 without having to fix custom/external layout-dependencies. @@ -2574,21 +2449,26 @@ Protocol to be used when calling web service. - + - Custom proxy address, include port separated by a colon + (optional) root namespace of the XML document, if POST of XML document chosen. (see and ). - + - Encoding. + Proxy configuration when calling web service - + Web service URL. + + + Value of the User-agent HTTP header. + + Value whether escaping be done according to the old NLog style (Very non-standard) @@ -2609,14 +2489,14 @@ Name of the root XML element, if POST of XML document chosen. If so, this property must not be null. (see and ). - + - (optional) root namespace of the XML document, if POST of XML document chosen. (see and ). + Encoding. - + - Proxy configuration when calling web service + Custom proxy address, include port separated by a colon @@ -2656,39 +2536,39 @@ - - - - - - - - + + + + + + + + - + - Footer layout. + Custom column delimiter value (valid when ColumnDelimiter is set to 'Custom'). - + - Header layout. + Column delimiter. - + - Body layout (can be repeated multiple times). + Footer layout. - + - Custom column delimiter value (valid when ColumnDelimiter is set to 'Custom'). + Header layout. - + - Column delimiter. + Body layout (can be repeated multiple times). @@ -2709,6 +2589,13 @@ + + + + + + + @@ -2720,70 +2607,92 @@ - - - - - - - - - + + + + + + Name of the column. + + Layout of the column. - + - Name of the column. + Override of Quoting mode - + - - - - - - - - + + + - + - List of property names to exclude when is true + Option to render the empty object value {} - + + + Option to suppress the extra spaces in the output json + + + + + + + + + + + + + + + + + + + + + Option to include all properties from the log event (as JSON) - + Indicates whether to include contents of the dictionary. - + - Indicates whether to include contents of the dictionary. + Whether to include the contents of the dictionary. - + - Option to render the empty object value {} + Should forward slashes be escaped? If true, / will be converted to \/ - + - Option to suppress the extra spaces in the output json + Option to exclude null/empty properties from the log event (as JSON) + + + + + List of property names to exclude when is true @@ -2791,30 +2700,53 @@ How far should the JSON serializer follow object references before backing off + + + Option to render the empty object value {} + + + + + Option to suppress the extra spaces in the output json + + - - - - - + + + + + + + + + + + Name of the attribute. + + Layout that will be rendered as the attribute's value. - + - Name of the attribute. + Fallback value when result value is not available - Determines wether or not this attribute will be Json encoded. + Determines whether or not this attribute will be Json encoded. + + + + + Should forward slashes be escaped? If true, / will be converted to \/ @@ -2827,14 +2759,19 @@ Whether an attribute with empty value should be included in the output + + + Result value type, for conversion of layout rendering output + + - - - + + + @@ -2858,35 +2795,60 @@ - - - - - + + + + + + + + + + - + Option to include all properties from the log events - + - Indicates whether to include contents of the dictionary. + Whether to include log4j:NDC in output from nested context. - + - Indicates whether to include contents of the dictionary. + Whether to include log4j:NDC in output from nested context. - + + + Whether to include the contents of the properties-dictionary. + + + - Indicates whether to include contents of the stack. + AppInfo field. By default it's the friendly name of the current AppDomain. - + - Indicates whether to include contents of the stack. + Indicates whether to include call site (class and method name) in the information sent over the network. + + + + + Indicates whether to include source info (file name and line number) in the information sent over the network. + + + + + Log4j:event logger-xml-attribute (Default ${logger}) + + + + + Whether the log4j:throwable xml-element should be written as CDATA @@ -2896,7 +2858,7 @@ - + @@ -2906,12 +2868,224 @@ + + + + + + + + + + + + + + + + + + + + + + + Name of the root XML element + + + + + Value inside the root XML element + + + + + Whether to include the contents of the dictionary. + + + + + Determines whether or not this attribute will be Xml encoded. + + + + + List of property names to exclude when is true + + + + + Whether a ElementValue with empty value should be included in the output + + + + + Auto indent and create new lines + + + + + How far should the XML serializer follow object references before backing off + + + + + XML element name to use for rendering IList-collections items + + + + + XML attribute name to use when rendering property-key When null (or empty) then key-attribute is not included + + + + + XML element name to use when rendering properties + + + + + XML attribute name to use when rendering property-value When null (or empty) then value-attribute is not included and value is formatted as XML-element-value + + + + + Option to include all properties from the log event (as XML) + + + + + + + + + + + + + + + + + Name of the attribute. + + + + + Layout that will be rendered as the attribute's value. + + + + + Fallback value when result value is not available + + + + + Determines whether or not this attribute will be Xml encoded. + + + + + Whether an attribute with empty value should be included in the output + + + + + Result value type, for conversion of layout rendering output + + + + + + + + + + + + + + + + + + + + + + + + Name of the element + + + + + Whether to include the contents of the dictionary. + + + + + Value inside the element + + + + + Determines whether or not this attribute will be Xml encoded. + + + + + List of property names to exclude when is true + + + + + Whether a ElementValue with empty value should be included in the output + + + + + Auto indent and create new lines + + + + + How far should the XML serializer follow object references before backing off + + + + + XML element name to use for rendering IList-collections items + + + + + XML attribute name to use when rendering property-key When null (or empty) then key-attribute is not included + + + + + XML element name to use when rendering properties + + + + + XML attribute name to use when rendering property-value When null (or empty) then value-attribute is not included and value is formatted as XML-element-value + + + + + Option to include all properties from the log event (as XML) + + + - - + + @@ -2939,10 +3113,10 @@ - - - - + + + + @@ -2971,10 +3145,10 @@ - - - - + + + + @@ -3003,10 +3177,10 @@ - - - - + + + + @@ -3035,10 +3209,10 @@ - - - - + + + + @@ -3067,26 +3241,30 @@ - - - - - - - - - - - + + + + + + + + + + Action to be taken when filter matches. - + - Default number of unique filter values to expect, will automatically increase if needed + Append FilterCount to the when an event is no longer filtered + + + + + Insert FilterCount value into when an event is no longer filtered @@ -3099,11 +3277,6 @@ Layout to be used to filter log messages. - - - Max number of unique filter values to expect simultaneously - - Max length of filter values, will truncate if above limit @@ -3114,24 +3287,19 @@ How long before a filter expires, and logging is accepted again - - - Default buffer size for the internal buffers - - - + - Reuse internal buffers, and doesn't have to constantly allocate new buffers + Default number of unique filter values to expect, will automatically increase if needed - + - Append FilterCount to the when an event is no longer filtered + Max number of unique filter values to expect simultaneously - + - Insert FilterCount value into when an event is no longer filtered + Default buffer size for the internal buffers diff --git a/cybersource-rest-samples-csharp.csproj b/cybersource-rest-samples-csharp.csproj index 7604422..3ec134e 100644 --- a/cybersource-rest-samples-csharp.csproj +++ b/cybersource-rest-samples-csharp.csproj @@ -53,9 +53,9 @@ packages\Newtonsoft.Json.13.0.1\lib\net45\Newtonsoft.Json.dll True - - packages\NLog.4.5.10\lib\net45\NLog.dll - True + + packages\NLog.5.0.0\lib\net46\NLog.dll + True packages\RestSharp.108.0.3\lib\netstandard2.0\RestSharp.dll diff --git a/cybersource-rest-samples-netcore.csproj b/cybersource-rest-samples-netcore.csproj index c8f126e..e6d9f81 100644 --- a/cybersource-rest-samples-netcore.csproj +++ b/cybersource-rest-samples-netcore.csproj @@ -43,8 +43,8 @@ - - + + diff --git a/packages.config b/packages.config index 154671a..35be05d 100644 --- a/packages.config +++ b/packages.config @@ -5,9 +5,9 @@ - + - +