IBM Support

QRadar: DSM Editor and custom log source cases and support policies

Question & Answer


Question

This article informs administrators about QRadar® Support policies related to Custom Log Source Types created that use the DSM Editor or through legacy XML extensions. For Log Sources that do not have an official DSM, use a custom Log Source type to integrate Log Sources. A Log Source extension (also known as a device extension) is then applied to the custom Log Source type to provide the logic for parsing the logs. The Log Source extension is based on Java™ regular expressions and can be used against any protocol type, such as syslog, JDBC, and Log File. Values can be extracted from the logs and mapped to all common fields within IBM® QRadar®.

Answer

Responsibilities for Custom Log Sources and DSM editor issues

The DSM editor allows an administrator to create a custom parsing scheme when a custom Log Source is required. This document outlines out-of-scope work for custom Log Source cases and the responsibilities of the QRadar administrator.

Support type Description Responsibility
Custom Log Source, DSM editor, and support
QRadar technical support teams can assist administrators with errors, questions, and issues, such as:
  1. Functional issues related to the DSM Editor. For example,
    • The DSM editor abnormally closes or generates error messages when you attempt to open the user interface.
    • Data does not display correctly or issues where the user interface does not display as expected in supported browsers.
    • Issues where the DSM Editor fails to save a configuration change to a log source.
    • Review errors in the QRadar logs for administrators.
    • An advanced configuration option in the DSM Editor is not functioning as expected when enabled or disabled.
  2. Specific queries related to the universal DSM functionality. For example,
    • Support can assist users and explain APARs related to the DSM Editor. 
    • Explain documentation and review cases where users locate issues with IBM Documentation for the DSM Editor.
    • The support representative can answer questions related to how mapping or custom properties work in the DSM Editor user interface.
    • QRadar Support can explain how advanced parsing options in the DSM Editor modify parsing in official IBM provided DSMs.
 QRadar technical support

To open a case or report a Log Source error, contact QRadar technical support.
Out-of-scope for QRadar Support Administrators are responsible for custom Log Source types created in the DSM Editor.

The following activities are considered out-of-scope for technical support cases:
  1. Requests for assistance to write, modify, test, or tune custom log sources for administrators in the DSM Editor.
  2. QRadar Support does not validate or update regular expressions to override default event properties for custom log sources.
  3. Requests to create custom event properties in the DSM Editor.
  4. QRadar Support does not assist users with mapping events or creating custom QIDs for events in the DSM Editor.
Administrators need to create, tune, test, and maintain custom Log Sources by referring to the documentation.
  1. Creating a Log Source extensions document to get data into QRadar.
  2. DSM Editor overview.
  3. Creating a Custom DSM.

[{"Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwsyAAA","label":"Admin Tasks"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Document Information

Modified date:
29 June 2021

UID

ibm16427787

Page Feedback