You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Event log entries have the IP address in one of the child Data elements inside the EventData element.
Currently, there are two ways to specify which Data element to search for the IP address in:
by name, if the Data element happens to have a Name attribute, set ipAddressEventDataName to the attribute value (e.g. payload)
<EventData>
<DataName="process">sshd</Data>
<DataName="payload">Failed password for invalid user foo bar from 192.168.1.7 port 49721 ssh2</Data>
</EventData>
the first one, if the Data element does not have a Name attribute
<EventData>
<Data>Failed password for invalid user foo bar from 192.168.1.7 port 49721 ssh2</Data>
</EventData>
This does not handle the case where there are multiple unnamed Data elements, and the IP address is not in the first one.
Event log entries have the IP address in one of the child
Data
elements inside theEventData
element.Currently, there are two ways to specify which
Data
element to search for the IP address in:Data
element happens to have aName
attribute, setipAddressEventDataName
to the attribute value (e.g.payload
)Data
element does not have aName
attributeThis does not handle the case where there are multiple unnamed
Data
elements, and the IP address is not in the first one.I can think of two approaches that may help:
ipAddressEventDataName
is empty, iterate through all childData
elements until a match is found, instead of only looking at the first one3
, not just theName
attribute valueThe text was updated successfully, but these errors were encountered: