In order to effectively manage ImgArchive, it is necessary to get feedback about the activity and performance of the running application as well as any problems that may be occurring. The ImgArchive provides very comprehensive and flexible logging capabilities. This section describes how to configure its logging capabilities, and how to understand what the logs contain.
When an ImgArchive application executes a task it outputs is process to a log file and optionally to the console and event network connection.
For each of these the format of the output are handled differently as the information needs to be presented to for fill different requirements. For example:
The file format
What Is a Logging File
Put simply, an application log is a file that contains information about events that have occurred within a software application. In this case ImgArchive These events are logged out by the ImgArchive tools and written to the file. They can include errors and warnings as well as informational events.
A log level or log severity is a piece of information telling how important a given log message is. It is a simple, yet very powerful way of distinguishing log events from each other. If the log levels are used properly in your application all you need is to look at the severity first. It will tell you if you can continue sleeping during the on-call night or you need to jump out of bed right away and hit another personal best in running between your bedroom and laptop in the living room.
Log Levels
Log Level adjusts the verbosity of the messages recorded in the log Files. The following levels are available, in order of increasing significance:
TRACE - low
FINE
INFO
STATUS
SUMMARY
WARNING
ERROR
FATAL
default is SUMMARY
TRACE – the most fine-grained information only used in rare cases where you need the full visibility of what is happening in ImgArchive You can expect the TRACE logging level to be very verbose. You can use it for example to capture every thing ImgArchive is doing.
DEBUG – less granular compared to the TRACE level, but it is more than you will need in everyday use. The DEBUG log level should be used for information that may be needed for diagnosing issues and troubleshooting or when running application in the test environment for the purpose of making sure everything is running correctly
INFO – the log level indicating that something happened, ImgArchive entered a certain state, etc. For example, Started processing an image The information logged using the INFO log level should be purely informative and not looking into them on a regular basis shouldn’t result in missing any important information.
STATUS – the log level indicating the status of the operation, ImgArchive entered a certain state, etc. For example, Started processing a new image with 342 images to complete
SUMMARY– the log is a final report on what transpired in the last operation.
ERROR – the log level that should be used when the application hits an issue preventing one or more functionalities from properly functioning.
FATAL – the log level that tells that the application encountered an event that it cannot continue and must stop and complete.
Log Outputs
The Application log is by default to both a log file and the Console. Logging to the Console screen may be not wanted or not required. This output can be suppressed. In addition file and console log levels may be set independently.
Setting Log level
This can be ... the environment variable SIA_LOGLEVEL
Command Line
These are the options that relate to the logging functions. Logging message can go both to the log file and or the the console screen.
quiet
--quiet (-q) Requests that the SIA print only essential information while performing an operation. default = false
silent
--silent (-s) Suppresses all messages during run that are normally sent to the console. silent = false
Log Level
--LogLevel (-l) The log level determines the granularity of the message that is logged, from fatal only (FATAL) to detailed debug (FINEST). The following values apply: SEVERE, WARNING, INFO, CONFIG, FINE, FINER, and FINEST. These log levels are hierarchically inclusive, which means that if you set a particular log level, such as INFO, the messages that have log levels above that level (SEVERE and WARNING) are also included. If you set the log level to the lowest level, FINEST, your output will include all the messages in the file. The log level can be set for both the console screen and the log file. The default setting is SUMMARY. default = "SUMMARY";
consoleLevel;
Log