Use the Lookup Processor to define a mapping between a log attribute and a human readable value saved in the processors mapping table. For example, you can use the Lookup Processor to map an internal service ID into a human readable service name. Alternatively, you could also use it to check if the MAC address that just attempted to connect to the production environment belongs to your list of stolen machines.

Hierarchy

  • LogsLookupProcessor

Constructors

Properties

additionalProperties?: {
    [key: string]: any;
}

A container for additional, undeclared properties. This is a holder for any undeclared properties as specified with the 'additionalProperties' keyword in the OAS document.

Type declaration

  • [key: string]: any
defaultLookup?: string

Value to set the target attribute if the source value is not found in the list.

isEnabled?: boolean

Whether or not the processor is enabled.

lookupTable: string[]

Mapping table of values for the source attribute and their associated target attribute values, formatted as ["source_key1,target_value1", "source_key2,target_value2"]

name?: string

Name of the processor.

source: string

Source attribute used to perform the lookup.

target: string

Name of the attribute that contains the corresponding value in the mapping list or the default_lookup if not found in the mapping list.

Type of logs lookup processor.

Generated using TypeDoc