Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Viewing Your App Logs


Use built-in routes to create HTTP requests download, view, and set log collection levels.

You can create your own targeted web requests to the app for the following routes:

Table 1: Request Routes




GET /debug

GET https://<console_ip>/console/plugins/ {application_id}/app_proxy/debug

Download your /store/log/app.log file from inside the container for inspection.

GET /debug_view

GET https://<console_ip>/console/plugins/ {application_id}/app_proxy/debug_view

Display the contents of the /store/log/app.log file inside your browser window.

POST /log_level

POST https://<console_ip>/console/plugins/ {application_id}/app_proxy/log_level form body: level = 'INFO' 'DEBUG' 'ERROR' 'WARNING' 'CRITICAL'

Dynamically define the level of logging that you want your app to capture. Post a form, with an attribute level that is set to one of the log level values to this endpoint. JSA dynamically reset the log collection levels in your /store/log/app.log file.

The application_id is the integer value that is assigned when you use the installation RESTful endpoints for GUI app creation. The application_id value is recorded in the Application Creation Task state output that is returned when you run the qradar_app_creator deploy command.

Viewing Logs Within the Host Directory

Alternatively, you can use the /opt/qradar/support/ utility to view your app logs by using its internal shell.

All logs are located in the /store/log directory of the container.

For more information about how to obtain the container ID, see Accessing Your App's Command Line.

Related Documentation