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 since katl-commons starting with SIL Engine™ 2.5. |
Syntax
...
logPrint(logLevel, #{message})
Description
...
Excerpt |
---|
This routine is used to print Prints a message in the configured JIRA 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 plugin 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
To configure the
...
Jira Logging level
...
do this in two ways:
...
Temporarily -
...
the logging level will be reset after
...
Jira reboot
...
:
...
- 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.
...
- 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 reboot
...
, described here:
...
Example
Example
Code Block |
---|
logPrint("DEBUG", "A debug Message."); |
If the configuration level is one
...
of TRACE or DEBUG then the message will be printed out.
Otherwise
...
if the configuration level
...
is INFO, WARN, ERROR or FATAL the
...
message will not be displayed.
For other usages you can consult the priority level list above.
See also
...
Filter by label (Content by label) | ||||||||
---|---|---|---|---|---|---|---|---|
|