Discovery Tab
To access the Discovery tab, go to NetWitness (Admin) > Event Sources. The Discovery tab is displayed.
The Discovery tab lets you review the event source types that NetWitness has discovered for each address and the system’s confidence of how likely it is that they were identified completely accurately. If the discovered event source types are correct, you can acknowledge to filter out that event source. If incorrect, you can set the allowed event source types for a particular address so that future logs will parse against the correct parsers.
NetWitness automatically maps incoming events to a type based on previous logs received from that address, reducing the mis-parsing of messages and reducing the number of items that need attention in the Discovery workflow. A value of Auto in the Mapping Type column indicates that an address has been auto-mapped.
Workflow
This workflow shows the overall process for configuring event sources.
What do you want to do?
Role | I want to... | Documentation |
---|---|---|
Administrator |
Acknowledge and map event sources.* |
|
Administrator |
Add and configure parser mappings for a Log Decoder.* |
|
Administrator |
View event source alarms. |
|
Administrator |
Troubleshoot event source management. |
*You can perform this task here.
Related Topics
Quick Look
The following example displays a list of addresses and their discovered Event Source types. The Event Source types display the Event Sources that have been discovered.
This is an example of the tab.
1 |
Displays the Filters and Event Sources panels with the Discovery tab open. |
2 |
Displays the Event Source Filter field with a drop-down menu that offers the following options:
Note: When specifying the search string, you can use . - : (period, dash, colon). |
3 | The Event Source Type drop-down menu filters for addresses containing all of the selected event source types. |
4 |
Note: If no mapping filter options are selected, the default is to display All, None, Manual, and Auto mapping types. |
5 |
|
6 | Toggles the event sources between acknowledged and not acknowledged states. |
7 | Maps the selected event sources. |
8 | View Details button to view details of the selected Event Source. |
9 | Displays the addresses of the selected Event Sources. |
10 | Displays the discovery scores of the selected Event Sources. |
11 | Displays whether or not the selected Event Sources have been acknowledged. |
12 | Displays the selected Event Source Mapping type as Auto, Manual, or None. Any changes to the mapping are only displayed here. |
13 | Displays the host names of the Log Collectors where the Event Sources are located. |
14 | Displays the host names of the Log Decoders where the Event sources are located. |
15 | Displays the discovered Event Source Types and their associated discovery scores. |
Toolbar and Features
The Discovery tab contains the following features:
Field | Description |
---|---|
Tools
|
The following items are available on the toolbar:
|
Event Source |
The IP, IPv6, or Hostname of the Event Source. |
Discovery Score |
Displays the overall discovery score associated with that particular address. Higher scores indicate better confidence. Discovery scores range from 0 (least confident) to 100 (most confident). |
Acknowledged |
Selections are either Yes (you have acknowledged the Event Source) or No (you have not acknowledged the Event Source). |
Mapping Type |
Selections are Manual (you mapped the Event Source), Auto (the system automatically mapped the Event Source), or None (you have not mapped the Event Source). Auto mapping is content aware. When a log message is parsed to a high confidence header or message that has been tagged, an auto mapping will be set for that address and type. This auto-mapping is valid for 24 hours and will be renewed every time a log message matches a tagged header of a message. Log messages are first parsed against auto-mapped parsers, and only fall back to discovery if there is no match amongst the mapped parsers. Log messages that fall back to discovery can match the tagged headers or messages from other event sources: this results in multiple types being mapped. For example, an address could eventually be mapped to Windows, MS SQL, and Apache, and these parsers are evaluated first. If an event source is decommissioned, and its IP re-purposed, the 24-hour timer ages out the mappings for the decommissioned types. Note: This feature applies to NetWitness latest version. |
Log Collector(s) |
Log Collectors that have received logs from this Event Source address. |
Log Decoder(s) |
Log Decoders that have received logs from this Event Source address. |
Event Source Type(s) |
The parsed type(s) of the Event Source address and the corresponding Discovery Score for each type. |
The following table describes the sorting order for discovery scores. To access the Sorting Order drop-down menu, click on the down arrow in the Event Sources column.
Field | Description |
---|---|
Sort Ascending |
Sort the column by discovery score in ascending order. |
Sort Descending |
Sort the column by discovery score in descending order. |
Columns |
Used to hide or show one or more columns. |