This document describes the IBM QRadar 7.4.0 Application Framework Guide.
IBM QRadar 7.4.0 Application Framework Guide describes how to develop QRadar apps that extend a QRadar deployment with new data and functionality. Apps are Python Flask applications that serve endpoints from a secure container and inject content such as tabs, dashboard items, toolbar buttons, and configuration pages into the QRadar user interface. The document covers the app file and manifest structure, the QRadar App Editor, SDK installation and development environment, packaging and deployment, OAuth authorization, multitenancy, sample apps, logging, globalization, custom actions, and custom AQL functions.
It is for maintaining apps built with CentOS, Python 2, and QRadar App Framework version 1; newer apps built using Red Hat Universal Base Image (UBI) 8 and Python 3 use App Framework version 2 documentation. The guide also notes that IBM X-Force Exchange no longer accepts new apps that use App Framework version 1.
| App framework version | version 1 |
|---|---|
| App programming language | Python |
| Web framework | Flask |
| App packaging format | Compressed archive (.zip) |
| Combined app memory limit | 10 per cent of total available memory |
A QRadar app is a small plug-in module to the GUI Application Framework that serves endpoints from within a secure container and injects content into the QRadar web interface.
Apps are packaged as compressed archives (.zip) within the extension archive.
The combined memory requirements of all apps on a QRadar Console cannot exceed 10 per cent of the total available memory; an app that causes this limit to be exceeded does not work.
No. Apps cannot use the proxy support built into QRadar; if an app requires internet access, it must implement proxy support itself.