logsettings.json Parameters - ironstream_for_elastic - ironstream_for_splunk - Ironstream_Hub - ironstream_for_kafka - 1.3

LogType

User logs have these characteristics:

• Messages about the operation of the product that can be understood by the user.
• They will be written in the localized language of the server, if a language pack for the server’s language exists within product.

Trace logs have these characteristics:

• For use by Precisely developers and support engineers for the purpose of diagnosis.
• All User Logs messages will appear within Traces.
• All Trace messages will be written in the Developer lingua franca – English.
• The stack trace whenever the program encounters a critical system error.
• Includes the monitoring details providing pipeline status values and other metrics.

LogLevel

The maximum level of messages that will be written by the log.

For example, if LogLevel is set to Info, then it will write all messages that are Info, Warning, and Error. It will not write Verbose messages.

Format

Logs can be written in Text or Json format.

For JSON - more easily consumed by log parsing software such as Splunk or Log Stash.

For Text - more easily readable by humans.

OutputTarget

If Hub is running in a Docker container it may be useful to write to standard output and standard error. This ensures that the logs are available using the docker log command.

When OutputTarget is set to File the presence of a LogFileSettings key/value pair is mandatory. The fields of the LogFileSettings object can be found in the table below. The fields are mandatory.

Files generated by using the File target are created in the Log Directory.