Tired of digging through your server to access logs? The newest version of Power Scripts for Jira makes debugging easier than ever. With a new in-built log viewer, Jira admins can finally save time by checking logs and writing scripts simultaneously. 

This in-demand upgrade comes with SIL engine 4.1.3. No extra setup or installation required—just update your Power Scripts for Jira app, and you will be on your way.  

As a developer, you know how vital it is to test scripts during development. The new in-built log viewer makes it easier than ever to catch and fix errors before they snowball into more serious issues. With Jira’s log viewer, debugging is faster, easier, and more efficient: 

  • View your log files: To save you effort and time, you can browse logs directly in SIL Manager
  • Search and filter your logs:  Limit the log output to relevant entries with filter and search features. 
  • Simplify your file selection:  Quickly select and view any file from the log directory without accessing the server. 

Get started with two easy steps. 

How to access the log viewer

There are only two simple steps to start using the new log viewer. 

  1. Install the latest version of Power Scripts for Jira. SIL Engine will install automatically after installing Power Scripts. Make sure you’re running a minimum version of  SIL Engine 4.1.3.
  2. Go to administration > Add-ons and select SIL Manager in the CPRIME Tools section. There, you’ll see the log viewer section at the bottom. 

Screenshot of SIL manager

It’s as simple as that!

The new log viewer introduces many other time-saving features

Easily search and filter script errors

Users can also easily define how many entries they want to view in the log viewer. You can also conveniently arrange their order, newest to first.   Query by specific search terms to read log notes more effectively. Search terms can be case-sensitive or a direct match.

Screenshot of Jira log viewer settings

Take advantage of powerful runtime logging

Jira also uses a powerful logging module, log4j, used for runtime logging. These logs are written to the log subdirectory Jira Application Home Directory. Jira Home Directory contains vital data that controls your Jira environment.

It has various files and subdirectories inside it. Once you install Jira for Windows or Linux, the default location of the home directory is:

For Windows

 

  • C:\Program Files\Atlassian\Application Data\JIRA

 

For Linux

 

  • /var/Atlassian/application-data/Jira

 

Logging Levels

Log4j has five logging levels. Each level provides more logging information than the level before it:

  • DEBUG
  • INFO
  • WARN
  • ERROR
  • FATAL

You can change default logging levels: 

  • Temporarily: Changes will revert back to default on the next restart of Jira
  • Permanently: Keep changes in place even after the next restart of Jira.

Print the logs using a different level by using “logPrint” Syntax:

  • logPrint(logLevel, #{message})

You can configure this with different levels depending on the use case. 

Debug scripts fast 

Log viewer from Power Scripts for Jira enables users to debug and troubleshoot their scripts more easily and efficiently without any hassle. Try it for yourself now: download the latest version of Power Scripts here.



Tagged with:

Categorized in: ,