IBM Support

QRadar: Why qradar.error log file spans a short period of time?

How To


Summary

If a qradar.error log file has a life span less than 24 hours it could be a strong indication, that one of the QRadar components is generating enormous number of errors. Resulting in a logrotate issue or an inability to collect the system logs for a longer time period. Extremely severe conditions are when the qradar.error time span covers only a few minutes. Many QRadar administrators are not aware that a persistent issue might be running on their system, concurrently with other problems that they are currently investigating.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSV4BL","label":"IBM QRadar"},"ARM Category":[{"code":"a8m0z000000cwtNAAQ","label":"Deployment"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.3.0;7.4.0;7.5.0"},{"Product":{"code":"SSTZMA","label":"QRadar Appliance Hardware"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":" ","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB77","label":"Automation Platform"}}]

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.

Document Information

Modified date:
03 April 2023

UID

ibm16955011