Set Logging Window
The logging levels are the same for Riva logs, Splunk logs, and JSON logs.
Definitions of the logging levels.
Logging to Splunk
Logging to Splunk is optional. The following forms of logging to Splunk are supported:
- Activity logging.
- Diagnostic logging.
- Performance logging.
For every selected form of logging, the following Splunk appender settings are required.
(For activity logging, one more setting is available, at the end of the list.)
- URL: [Protocol]://[Host]:[Port]/Services/Collector/event
- Protocol: HTTP or HTTPS, depending on the global options of the instance that were specified at substep 4 when creating the collector's information.
- Best Practice: HTTPS is always recommended.
- Host: The host of the Splunk instance. Examples: localhost, 10.10.10.10.
- Port: The port used by the Splunk services, as specified at substep 4 when creating the collector's information.
- Token: The collector's token displayed after substep 8 when creating the collector's information.
- Source Name: The collector's source, as specified at substep 4 when creating the collector's information. In case it was not specified, use default.
- Index: The Splunk index that this appender will use.
- For activity logging only: Enable PII for Activity Log: (Default: [Cleared.])
- When the check box is cleared, Personally Identifiable Information (PII) may be present in the activity logs.
- When the check box is selected, PII is prevented from entering the activity logs: The PII is hashed and it is the hash that is logged in Splunk or native Riva activity logs.
Accessing the Set Logging window
(Riva 2.4.42 or higher.)
To access the Set Logging window:
Start the Riva Manager application.
On the menu bar, select Tools, and then choose Set Logging Level.