Search result parse from the NetworkEvent, passed back to the client from LeagacySearchAssetEvents.
JSON representation |
---|
{ "event_time": string, "domain": string, "chip": { object ( |
Fields | |
---|---|
event_ |
Date/time of lookup (i.e. not the time that the event was ingested). Uses RFC 3339, where generated output will always be Z-normalized and uses 0, 3, 6 or 9 fractional digits. Offsets other than "Z" are also accepted.Examples: |
domain |
Domain name looked up (i.e. "foo.bad-actor.com" or "foocompany.com"). |
chip |
The chip to display. |
http_ |
Additional details about HTTP requests associated with this lookup. |
resolved_ |
Either IPv4 or IPv6 results. Limited to a max of 5 results. We may want to annotate them with badges if the IPs are in a known IP space (CDN, AWS, Google Cloud, Rackspace, etc). |
customer_ |
The prevalence of the domain within the customer's environment, defined for v1 as the number of unique assets per day looking up the domain name over the trailing 10 days. |
filter_ |
A list of filter properties associated the event. |
raw_ |
A token to request raw logs, this is opaque to the client. If empty, no raw logs can be requested. |
sidebar_ |
All the sidebar entries. |
asset_ |
AssetIndicator used for pivoting. |