Troubleshooting
Problem
QRadar is using the network IP address of the event instead of using the hostname in the syslog header even when the events are RFC 5424 compliant.
Symptom
QRadar successfully creates log sources using the hostname information on the syslog header for RFC 3164 compliant events, but for RFC 5424 compliant events, it creates new log sources by using the packet IP address instead of hostname.
This situation could cause problems to get the events in the right log source, or when the same server sends events with different hostnames, instead of creating one log source for each hostname, QRadar sends all the events to the same log source.
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":"a8m0z000000cwt0AAA","label":"Log Source"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"},{"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.
Was this topic helpful?
Document Information
Modified date:
23 February 2024
UID
ibm17120763