The Logger schema contains a predefined set of fields. A field-based query can contain only these fields. Additionally, you can index only these fields for faster search operations. For instructions on how to view the default Logger schema fields, see Default Fields.
Prior to Logger 5.2, if your log analysis needs required you to search on a field that is currently not present in the Logger schema, you did not have a way of adding it to the schema yourself. Starting with Logger 5.2, you can add additional fields to the Logger schema. That is, you can insert fields in your Logger schema that are relevant to the events you collect on your Logger, thus enabling you to search and report using these fields. Additionally, you can index the fields you add so that the search and report queries that use these fields run faster. For example, a financial institution might want to add credit card numbers or social security numbers to the schema.
You can add up to 100 custom schema fields on Logger. You can also import custom fields from a peer Logger. However, the total number of added and imported fields cannot exceed the maximum allowed 100 fields.
You can index up to 123 fields on Logger. Therefore, the number of custom schema fields you can index will depend on the number of default fields you currently have indexed on your Logger.
Note: Logger cannot process the additional fields data received in CEF version 0 from a FlexConnector, and assumes a NULL value for such fields when they are present in a CEF version 0 event. As a result, you cannot search on these fields or index them. However, these fields are displayed in the UI display when you select “*” in the field set because the interface displays information contained in the raw event. Therefore, if Logger receives “ad.callnumber=5678”, the Logger UI will display a column, ad.callnumber, with value 5678. However, a search on “5678” will not return this event in the search results.
You need to be in maintenance mode to add or import custom schema fields. The process of adding or importing schema fields involves an add or import operation followed by a save operation. The add or import operation adds the specified fields but does not write them to the Logger schema. You can edit or delete the added or imported fields at this point. Once you save these fields, the fields are written to the schema. From this point on, these fields cannot be edited or deleted. Therefore, carefully review the fields you are adding to the schema before saving them.
Note: For the “Add Fields” operation to show as an option under the System Maintenance operations (Configuration > Advance > Maintenance Operations), you need to belong to the System Admin group (with “Enable Maintenance Mode” privilege enabled) and the Logger Rights group. See Users/Groups for more information on Logger user rights and how to administer them.
You need to specify the following information to add a custom schema field
Type — The type of data this field will contain. The available options are Double, BigInt, DateTime, Text.
The following table describes each data type.
|
Type |
Description |
|---|---|
|
Double |
Use to store decimal numbers or fractions. Numbers from
|
|
BigInt |
Use to store whole numbers. Numbers from ‑9,223,372,036,854,775,808 through 9,223,372,036,854,775,807. |
|
DateTime |
Use to store both dates and time or only dates. |
|
Text |
Use to store any characters. You can store a maximum of 255 characters per field. |
SSN.