Logline Filters


Today's networks generate an enormous quantity of traffic, not nearly all of which is of general interest or worthy of reporting. So the report engine attempts to discard requests that would only tend to clutter or obscure the traffic of real interest.

The list of default filters can be used as a guide to create new patterns. For example, if a company uses a cloud-based ERP or POS system, such traffic would overwhelm all the other traffic, load up the report database, and would be a prime candidate to filter out.


Pattern Types

The Pattern can be either a single alphanumeric string/sequence of characters or a JSON list of strings.


Filter Types

Equal - Single String

The "Equal" filter takes a single string sequence pattern and checks to see if the pattern exactly matches the Field. A pattern exactly matches the Field to fire. This filter is fast.

In - List of Patterns

When the "In" filter is given a List of Patterns, the Field is checked for an Exact Match to any pattern in the list. A pattern exactly matches the Field to fire. The list of patterns is hashed, so this filter is fast.

In - Single String

When the "In" filter is given a string sequence pattern to match, the Field is checked to see if the pattern occurs anywhere in the field. This filter uses sequential search and will be slower than the List of Patterns.

Contains - List of Patterns or Single String

The "Contains" filter performs the same whether given a single single pattern or list of patterns. The Field is checked to see if the pattern occurs anywhere in the field. This filter uses sequential search and will be slower than the List of Patterns.

Startswith/Endswith - List of Patterns or Single String

The "Startswith" and "Endswith" filters perform the same whether given a single single pattern or list of patterns. The Field is checked against the pattern(s) and matches if that Field either Startswith or Endswith that pattern. The pattern must match exactly to fire. This filter is fast.


Field Types

Hostname Field

The Hostname Field match against the Hostname of the URL, including the domain name and the local part. The section enclosed by the first set of slashes in the URL. "https://tickets.support.dell.com/path/to/resource"

Domain Name Field

The Domain Name Field match against the Domain Name of the URL - the Top Level Domain and the Second Level Domain. "https://tickets.support.dell.com/path/to/resource"

URL Field

The URL Field match against the entire URL string. URL patterns are the slowest and least precise, and should be used when no precise hostname or domain name pattern is possible.