Allows filtering by using an OData-like syntax with comparison and logical operators.


Filterable fields: call_id, interaction_id, user_id, timestamp, affected_call, packets_loss_percentage,
mos/avg, mos/min, mos/max, jitter/avg, jitter/max, rtt/avg, rtt/min, rtt/max.

Nested fields are referenced with a forward slash, e.g. mos/avg. The dot (mos.avg) and underscore (mos_avg) notations are not supported.

String and timestamp values must be wrapped in single quotes; timestamps use ISO 8601 format (e.g. '2020-12-18T13:09:09.417Z'). Numbers and booleans are not quoted.

Logical operators are and and or.

When using multiple ANDs and ORs, you should use parentheses to explicitly define the logical operators evaluation order.

(note: this is recommended because the usual precedence rules aren't supported due to an implementation detail).


Examples:

• mos/avg gt 0 and mos/avg lt 3
• affected_call eq true and packets_loss_percentage gt 5
• (contains(user_id, 'agent1') or contains(user_id, 'agent2')) and timestamp ge '2020-12-18T00:00:00.000Z'

Sorts by the indicated field in the specified direction, ascending or descending.

The expression format may contain the suffix asc or desc separated from the property name with a colon in between.

Nested fields are referenced with a forward slash, e.g. mos/avg:asc. The dot (mos.avg) and underscore (mos_avg) notations are not supported.

Records with null values come first in ascending order; combine with a filter such as mos/avg gt 0 to exclude calls without metrics.

Examples:

• timestamp:desc
• mos/avg:asc
• packets_loss_percentage:desc

Generated from available response content types