How To
Summary
A named service is a feature that allows other apps and parts of the QRadar UI to interact with an app. These named services can fit a variety of use-cases, including:
A background process exposing HTTP endpoints to query, such as a NodeJS express server.
A background process that does work within an app container without exposing endpoints.
Standard Flask endpoints grouped as a named service to allow them to be queried.
This page will explain how an app can interact with named services, which QRadar UI elements can make use of named services, and some notes on best practices with named services.
Document Location
Worldwide
[{"Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwt3AAA","label":"QRadar Apps"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
30 March 2021
UID
ibm16437515