use 1.0.5 in netcore3.1, I found a error:

Warn Unknown exception occured Exception: System.ArgumentException: Object must be the same type as the enum. The type passed in was 'System.Int32'; the enum type was 'System.Net.HttpStatusCode'.
at System.Enum.CompareTo(Object target)
at NLog.Targets.Http.HTTP.SendFast(String message)

and then my http log was repeat to called many times!

the flag _hasHttpError keeps TRUE after a http exception occurs or the http responsecode is not equal 200
so ProcessChunk method will not invoke anymore

Thank you for providing this extension to NLOG, the features and performance of which has been very useful to us.

We noticed one relatively minor performance problem with it. When idle, the background task has an infinite loop that polls a queue. On Windows, with a relatively high-spec i7 laptop this is no problem. No more than 0.5% of the CPU is ever consumed. On a Linux virtual machine, with many Docker containers, each container reports at least 30% CPU usage. We can of course discuss resource provisioning in Docker, and I am no expert in it, but I was able to fix the usage problem directly in your code.

I will attach a pull request to this issue in case you should find it useful.

Thank you for taking a look.

When using this library along with a JSONLayout batching and flushing create invalid json that causes a 400 request from the endpoint, because the json does not get wrapped in an array.

Code sample:
<target name='test' type='HTTP' URL='' Method='POST' BatchSize='3' FlushBeforeShutdown='true'> <layout type='JsonLayout'> <attribute name='sourcetype' layout='_json' /> <attribute name='host' layout='${machinename}' /> <attribute name='event' encode='false'> <layout type='JsonLayout'> <attribute name='level' layout='${level:upperCase=true}' /> <attribute name='source' layout='${logger}' /> <attribute name='thread' layout='${threadid}' /> <attribute name='message' layout='${message}' /> <attribute name='utc' layout='${date:universalTime=true:format=yyyy-MM-dd HH\:mm\:ss.fff}' /> </layout> </target>

Post request output (causes 400 bad request):
{"sourcetype":"_json", "host":"","event":{"level":"INFO", "source":"","thread:"1","message":"test","utc":"2021-10-05 15:01:01.375"}}
{"sourcetype":"_json", "host":"","event":{"level":"INFO", "source":"","thread:"1","message":"test","utc":"2021-10-05 15:01:01.375"}}
{"sourcetype":"_json", "host":"","event":{"level":"INFO", "source":"","thread:"1","message":"test","utc":"2021-10-05 15:01:01.375"}}

it doesn't retry when getting error

Great plugin, thanks for making it!

Quick question: what is the reason for not using async/await for http?

We'd like to use this package within a .NET Standard 2.0 library that's used across .NET Framework v4.7.2 and .NET Core based on the age of the projects.
We're seeing some warnings as the build is trying to use the .NET Framework version as there's no .NET Standard v2.0 version.

XXXXX.csproj: [NU1701] Package 'NLog.Targets.Http 1.0.7' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8' instead of the project target framework '.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.

use 1.0.5 in netcore3.1, I found a error:

Warn Unknown exception occured Exception: System.ArgumentException: Object must be the same type as the enum. The type passed in was 'System.Int32'; the enum type was 'System.Net.HttpStatusCode'.
at System.Enum.CompareTo(Object target)
at NLog.Targets.Http.HTTP.SendFast(String message)

and then my http log was repeat to called many times!

The documentation says that application/json is the default value for ContentType:

But this does not work as expected. If i omit the ContentType setting in my nlog configuration, the HTTP requests are sent with ContentType = null.

In the code, the _contentType field is initialized to the default value, but not _contentTypeHeader:

The latter is only set in the ContentType setter, which is never called if the setting is not specified in the configuration:

For the actual request, _contentTypeHeader is used, which is null in the default case:

I am trying to use this extension with the UiPath application to send log events to Splunk.

I've copied the extsension assembly to the UiPath Studio folder, where the NLog.dll resides, and updated the UiPath nlog.config file to reference the extension.

At runtime, I see the following error logged:

Exception: NLog.NLogConfigurationException: Failed to create Target of type: HTTP ---> System.ArgumentException: Target symbol-name is unknown: 'HTTP'
at NLog.Config.Factory2.CreateInstance(String itemName) at NLog.Config.LoggingConfigurationParser.FactoryCreateInstance[T](String classType, INamedItemFactory2 factory)

Any insights into what the problem might be would be greatly appreciated.

Here is my config file, with the Splunk token and URL removed:

<?xml version="1.0" encoding="utf-8" ?> <nlog autoReload="true" xmlns="http://www.nlog-project.org/schemas/NLog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" throwExceptions="true" internalLogFile="C:\Temp\nlog-internal.log" internalLogLevel="Trace" internalLogToConsole="true"> <extensions> <add assembly="NLog.Targets.Http"/> </extensions> <variable name="WorkflowLoggingDirectory" value="${specialfolder:folder=LocalApplicationData}/UiPath/Logs" /> <targets> <target xsi:type="File" name="WorkflowLogFiles" fileName="${WorkflowLoggingDirectory}/${shortdate}_Execution.log" layout="${time} ${level} ${message}" keepFileOpen="true" openFileCacheTimeout="5" concurrentWrites="true" encoding="utf-8" writeBom="true" /> <target name='splunk' xsi:type='HTTP' Url='splunkurl' Method='POST' Authorization='Splunk token' IgnoreSslErrors='true' FlushBeforeShutdown='true' ContentType='application/json' Accept='application/json' ConnectTimeout='30000' BatchSize='1'> <layout type='JsonLayout'> <attribute name='sourcetype' layout='_json' /> <attribute name='host' layout='${machinename}' /> <attribute name='event' encode='false'> <layout type='JsonLayout'> <attribute name='level' layout='${level:upperCase=true}' /> <attribute name='source' layout='${logger}' /> <attribute name='thread' layout='${threadid}' /> <attribute name='message' layout='${message}' /> <attribute name='utc' layout='${date:universalTime=true:format=yyyy-MM-dd HH\:mm\:ss.fff}' /> </layout> </attribute> </layout> </target> </targets> <rules> <logger name="WorkflowLogging" writeTo="WorkflowLogFiles" final="true" /> <logger name="*" minlevel="Debug" writeTo="splunk" /> </rules> </nlog>

This is probably not true, since WebServiceTarget is 20 years old (and uses legacy API and doesn't support batching):

But yes I have been thinking about creating a dedicated HttpClient-target, but also think this is a great project, so no need to compete with it.

We have installed later versions of the target, and it does not seem to send anything anymore. When we switch back to 1.0.10 things work fine.

everything from 11 to 14 does not work for us currently. There seem to be no exceptions/errors in the internal log

Thank you for providing a simple way to send log entries in batches to an HTTP endpoint, it's very simple to setup and get started.

One thing I noticed was that I seem to be getting double log entries sent to my data store. Everything logs successfully but I get the same logging statements twice.

I have the NLog configuration setup as a JSON file to point to an HTTP REST service. The REST service takes in the batch of log entries and is supposed to drop them into Couchbase. I am generating tasks for each log entry and waiting for all of them to complete, then returning a 200 OK status code.

At the end of the program execution, I am calling LogManager.Flush(TimeSpan.FromSeconds(60)) in a finally block to flush all log messages.

Using this target on .NET 5 appears to eat up ports. We are hitting the 128 port limit out on Azure App Service when we have this target turned on. It's not immediately obvious to me how we can mitigate this, so wanted to start the conversation.

I am looking for a way to add my own headers to http target requests but so far couldn't find any solution for that, is that something achievable in the current solution?

I'm trying to set the URL and Authorization parameters dynamically but they always end up being set as the placeholder ${var:MyVariable} or ${gdc:item=MyGdcItem} instead of the real value. Are they not supported?

The header value doesn't update. Layout value gets updated.
This would be useful in case of supplying metadata via header. The http target has BatchAsJsonArray="true" wrapped in BufferingWrapper.
custom layout render.
LayoutRenderer.Register("unixutcms", (logEvent) => DateTimeOffset.UtcNow.ToUnixTimeMilliseconds());

<header name="ClientUtcNowMs" value="${unixutcms}"/>
<layout type="JsonLayout" >
<attribute name="ts" layout="${unixutcms}" />
...

I'm not sure if the ${unixtime} layout is ready for use but I tried it out and it is rendering seconds based on local time instead of UTC time.

I have also tried setting the NLog time source to FastUTC and that doesn't make a difference.

Hello,

Problem

I've just setup a simple configuration using HTTP target, and I've noticed a relatively high CPU usage. A constant CPU usage of about 3% - 5% was observed.

Current Configuration

Nlog.config

<?xml version="1.0" encoding="utf-8"?>
<nlog
    xmlns="https://www.nlog-project.org/schemas/NLog.xsd"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <extensions>
        <add assembly="NLog.Targets.Http" />
    </extensions>
    <target name='http_target'
            type='HTTP'
            URL='https://url'
            Authorization='secret'
            BatchSize="50">
        <layout type='JsonLayout'>
            <attribute name='host' layout='${machinename}' />
            <attribute name='level' layout='${level:upperCase=true}' />
            <attribute name='message' layout='${message}' />
            <attribute name='timestamp' layout='${longdate:universalTime=true}' />
            <attribute name='meta_data' encode='false'>
                <layout type='JsonLayout'>
                    <attribute name='thread' layout='${threadid}' />
                    <attribute name='callsite' layout='${callsite:className=true:fileName=true:includeSourcePath=false:methodName=true}' />
                </layout>
            </attribute>
        </layout>
    </target>
    <rules>
        <logger name="*" minlevel="Error" writeTo="http_target" />
    </rules>
</nlog>

Investigation

It seems that changing timeToSleepBetweenBatches attribute didn't have any effect, I've tried to set it to value 0 or 1 and the problem remains.

After reading the source code, I've noticed a potential cause of this problem. For this line Http.cs#L254, it will wait for 1ms each time in the loop.
Does this mean the logger will be fired at least every 1ms ?

Environment

• dotnet 5.0.101
• NLog 4.7.9
• NLog.Targets.Http 1.0.5

Perhaps the problem happens because of a mis-configuration of the nlog.config, any help would be appreciated.

Thanks,
Charles Y

I'm try to install the dll on GAC, because we have many applications that will use it, but get the error:
"Failure adding assembly to the cache: Attempt to install an assembly without a strong name"

I want to write logs to an internal API that uses Windows authentication. Is this possible? I don't see anything in the docs and my API returns a 401.