On This Page
TQL Fields For USP Exceptions
The following fields are available via TQL.
All Fields
Field Name | Description | Field Type / Example Values |
---|---|---|
applications |
Excepted applications |
String |
approver |
Approver of the exception |
String |
description |
Exception description |
String |
destinations |
Excepted destinations |
String |
device.name |
Name of the device |
String |
disabled |
Is exception disabled? |
true, false |
domain.name |
Name of the domain to which the device has been assigned |
String |
ruleException |
Shows type of exceptions
|
true, false |
fromZone.name |
Excepted from zones |
String |
invalid |
Is exception invalid? |
true, false |
name |
Exception name |
String |
policy.name |
Name of the policy |
String |
rule.id |
Rule UID |
String |
rule.name |
Name of the rule |
String |
services |
Excepted services |
String |
sources |
Excepted sources |
String |
ticketId |
Ticket ID |
String |
timeCreated |
Date the exception was created |
YYYY-MM-DD |
timeEnd |
End date for exception to be active |
YYYY-MM-DD |
timeLastModified |
Date the exception was last modified |
YYYY-MM-DD |
timeStart |
Start date for exception to be active |
YYYY-MM-DD |
toZone.name |
Excepted to zone |
String |
trafficException |
Shows type of exceptions
|
true, false |
usp.name |
Names of excepted USPs |
String |
Sort Fields
Fields than can be used with the 'order by' operator.
- name
Query Examples
-
Review traffic exception for legacy servers - search for source destination and service of the exception.
sources = '192.168.1.1' and destinations = '10.100.1.1' and services in ('http', 'telnet') order by name