Admin: Logging
Overview
RPI outputs trace and error information to the Log table in the Pulse_Logging database. By default, only error messages are written to the database. For diagnostic purposes, sometimes it may be necessary to increase the amount of trace logging a service writes out. This can be done using the following setting:
Logging__Database__RPITrace=Information
Nlog logging
In addition to the standard logging configuration, RPI containers also support NLog (NLog (nlogproject.org)). NLog can be used to configure the services to output to any of the logging targets supported by NLog. This includes logging directly to a file.
To configure NLog at any of the RPI services’ appsettings.json files, please see the following link: https://github.com/NLog/NLog.Extensions.Logging/wiki/NLog-configuration-with-appsettings.json
Azure Monitor logging
It is possible to configure any of the RPI services to log application trace and error logging via Azure Application Insights for viewing via the Azure Monitor portal (examples given are environment variables):
Logging__ApplicationInsights__ConnectionString=connection-stringLogging__ApplicationInsights__LogLevel__Default=Information
Please see Application Insights overview - Azure Monitor | Microsoft Learn for more details.
NewRelic/Loggly logging
RPI supports the logging of messages to the NewRelic and Loggly providers. These can be configured using the following (examples given are environment variables):
Logging__NewRelic__Enabled=true
Logging__NewRelic__ApiKey=[xxx]
Logging__NewRelic__OptionalAttributes__0=[aaa]
Logging__Loggly__Enabled=true
Logging__Loggly__ApiKey=[yyy]
Logging__Loggly__OptionalAttributes__0=[b]
The above examples include optional attributes, which can be written alongside RPI logs and used as a basis for filtering within the respective tools.