Overview¶

The AOC enables multi-dimensional analysis of data through Groups and Filters features for queries.

GroupBy¶

As the name suggestes, GroupBy will create grouping of data points based on specified attributes. For e.g., for datasource http.request_response.latency (i.e latency for all HTTP services), we can use URI Path attribute to group the latency data. This will provide average latency for HTTP services serving the URI resources. Further more, we can combine Groups feature with Top function to find out the top 3 services experiencing highest average latencies. (Please consult datasources documentation for details on datasource and their attributes.)

GroupBy

Filters¶

Filters enable selection and elimination of data points based on multiple criteria. There are 3 types of filters available while building queries in Application Operations Center (AOC).

Filters

Filter by Field of Datasources¶

In AOC, every datasource has many specific fields (or attributes). For e.g. HTTP datasources have HTTP Status Code, URI Path, etc and MySQL datasources have Query Type, Error Codes, etc. These attributes are valuable to filter data in queries. For e.g., we can filter HTTP Latency by HTTP Status Code = 200, to identify the latency of successful HTTP requests.

When multiple filters are used the following rule applies to combine them:

Filters on same fields are combined using "OR". For e.g, filter on HTTP Status Code = 200 or HTTP Status Code = 500
Filters on different fields are combined using "AND". For e.g., (filter on HTTP Status Code = 200 or HTTP Status Code = 500) and (Server = 10.0.105.118)

(Please consult datasources documentation for details on datasource and their attributes.) Filter by Field of Datasources

Filter by Sub-Queries¶

AOC enables queries to filter based on results of sub-queries. Lets say we create a sub-query SQ1. To filter results using this sub-query, we just need to:

Select filter, Data field is in subquery
Select specific field to use for joining the results. For e.g. URI Path
Specify the sub*query name, SQ1, to use for filtering. The below example shows this with:
SQ1 : Returns top 3 HTTP URI paths experiencing highest average latency
Main Query: Uses the URI paths from SQ1 and generates throughput for these high latency services. (Please consult sub-query documentation for more details.)

Filter by Sub-Queries

For help please email epoch-support@nutanix.com