| Warning |
|---|
Looking for the documentation on the newest versions of SIL Engine and the Simple Issue Language for Jira 8 for Server/Data Center? Click here ! |
| Info | ||
|---|---|---|
| ||
This routine is available starting with katl-commons SIL Engine™ 2.5. |
Syntax
logPrint(logLevel, #{message})
...
| Excerpt |
|---|
Prints a message in the configured Jira logs on the specified level: TRACE, DEBUG, INFO, WARN, ERROR, FATAL. |
Logging the messages above messages is subject to the same configurations of the app as described here.
Parameters
Parameter name | Required | Description |
|---|---|---|
logLevel | Yes |
Minimum level for logging |
the message is written for. | |
| message | Yes |
| Argument converted to a string that will be printed. |
Return type
None
Configuration
...
- Log in Jira using an administrator account.
- Go to Administration.
- Go to System tab and select the Troubleshooting and Support option.
- Select the Logging & Profiling tab.
- Here you'll find a paragraph named Default Loggers with a lot of Find the Default Loggers paragraph with package names and their Logginglevel.
- Search in this list for the line com.keplerrominfo. And select from the Set Logging Level your desired level.
...
Permanently - the logging level will NOT be reset after JIRA Jira reboot, described here: Configure Jira logging.
...
Example
| Code Block |
|---|
logPrint("DEBUG", "A debug Message."); |
If the configuration level is one of: of TRACE or DEBUG then the message will be printed out.
Otherwise , if the configuration level is: is INFO, WARN, ERROR or FATAL the message will not be displayed.
...
| Filter by label (Content by label) | ||||||||
|---|---|---|---|---|---|---|---|---|
|