DRY up your log4net config by using these log4net Appenders with sensible defaults
- Add to your project using from Nuget -
Install-Package log4net.Appenders.Contrib - In your log4net config, add an additional appender:
<appender name="RemoteAppender" type="log4net.Appenders.Contrib.RemoteSyslog5424Appender,log4net.Appenders.Contrib">
<AppName>your app name</AppName>
<Hostname>LON-WS0000</Hostname>
<Server>ingestor.cityindex.logsearch.io</Server>
<Port>443</Port>
<Certificate>
-----BEGIN CERTIFICATE-----
MIIDBzCCAe+gAwIBAgIJAJ4oZAZ2ngs1MA0GCSqGSIb3DQEBBQUAMBoxGDAWBgNV
...
any valid self signed SSL certificate
- see below for how to generate a new one
...
Bmo1t/kphLKZnmo=
-----END CERTIFICATE-----
</Certificate>
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%-5p %d %t %c %m" /><!-- standard ci_log4net layout, WITHOUT the trailing newline-->
</layout>
<Field>type=ci_log4net</Field> <!-- trigger additional type:ci_log4net parsing-->
<Field>environment=DEV</Field> <!-- Decorate the message with additional structured data fields -->
<Field>user=$USERNAME</Field> <!-- $KEY_NAME will pull values from the current environment -->
</appender>
...
<root>
...
<appender-ref ref="RemoteAppender" />
</root>- Generate your own self signed certificate using http://www.selfsignedcertificate.com/, using any domain name, downloading the .cert file and opening with your favourite text editor
- Update
VERSION.txt - From a Powershell 4.0 prompt:
build.ps1
build.ps1 -nuget_api_key XXXXXX -nuget_api_url https://www.nuget.org/api/v2/package NugetPublish