-
-
Advanced Policy Expressions: Working with Dates, Times, and Numbers
-
Advanced Policy Expressions: Parsing HTTP, TCP, and UDP Data
-
Advanced Policy Expressions: IP and MAC Addresses, Throughput, VLAN IDs
-
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Grouping records on attribute values
Statistical information such as the number of times a particular URL has been accessed overall and per client, and the total number of GET and POST requests per client can provide valuable insights into whether any of your resources need to be expanded to meet the demand or be optimized for delivery. To obtain such statistics, you must use an appropriate set of selector expressions, and then use the pattern parameter in the stat stream identifier command. The grouping is based on the pattern that is specified in the command. Grouping can be performed concurrently on the values of multiple expressions.
In the command-line interface, you can group the output by using patterns of your choice. In the configuration utility, the pattern depends on the choices you make when drilling down through the values of various selector expressions. For example, consider a selector that has the expressions HTTP.REQ.URL
, CLIENT.IP.SRC
, and HTTP.REQ.LB_VSERVER.NAME
, in that order. The statistics home page displays icons for each of these expressions. If you click the icon for CLIENT.IP.SRC
, the output is based on the patterns ?. The output displays statistics for each client IP address. If you click an IP address, the output is based on the patterns * <IP address> ?
and ? <IP address> *
where <IP address>
is the IP address you selected. In the resulting output, if you click a URL, the pattern used is <URL> <IP address> ?
.
To group the records on the values of selector expressions by using the command line interface
At the command prompt, enter the following command to group the records on the basis of a selector expression:
stat stream identifier <name> [<pattern> ...]
The following examples use a different pattern to demonstrate the effect of the pattern on the output of the stat stream identifier command. The selector expressions are HTTP.REQ.URL and HTTP.REQ.HEADER(“UserHeader”), in that order. The requests contain a custom header whose name is UserHeader. Note that in the examples, a given statistical value changes as determined by the grouping, but the sum total of the values for a given field remains the same.
Example 1
In the following command, the pattern used is ? ?. The appliance groups the output on the values collected for both selector expressions. The row headers consist of the expression values separated by a question mark (?). The row with the header /mysite/mypage1.html?Ed displays statistics for requests made by user Ed for the URL /mysite/mypage1.html.
Note:
You must ensure to type the following command with “\?” instead of “?”. For example, If selector uses an expression - client.ip.src and client.tcp.srcport. The Stat command to group the output on the values collected for the selector is ‘stat stream identifier myidentifier \? \? -fullValues’ as given below.
> stat stream identifier myidentifier ? ? -fullValues
Stream Session statistics
Req BandW
/mysite/mypage2.html?Grace 1 2553
/mysite/mypage1.html?Grace 2 4
/mysite/mypage1.html?Ed 8 16
/mysite/mypage2.html?Joe 1 2554
/mysite/mypage1.html?Joe 5 10
/mysite/?Joe 1 4
RspTime Conn
/mysite/mypage2.html?Grace 0 0
/mysite/mypage1.html?Grace 0 0
/mysite/mypage1.html?Ed 0 0
/mysite/mypage2.html?Joe 0 0
/mysite/mypage1.html?Joe 0 0
/mysite/?Joe 6 0
Done
<!--NeedCopy-->
Example 2
In the following command, the pattern used is * ?. The appliance groups the output on the values accumulated for the second expression HTTP.REQ.HEADER(“UserHeader”). The rows display statistics for all requests made by users Grace, Ed, and Joe.
Note:
Ensure to type the following command with “\?” instead of “?”.
> stat stream identifier myidentifier * ?
Stream Session statistics
Req BandW RspTime Conn
Grace 3 2557 0 0
Ed 8 16 0 0
Joe 7 2568 6 0
Done
<!--NeedCopy-->
Example 3
In the following command, the pattern used is ? *, which is the default pattern. The output is grouped on the values collected for the first selector expression. Each row displays statistics for one URL.
Note:
Ensure to type the following command with “\?” instead of “?”.
> stat stream identifier myidentifier ? * -fullValues
Stream Session statistics
Req BandW
/mysite/mypage2.html 2 5107
/mysite/mypage1.html 15 30
/mysite/ 1 4
RspTime Conn
/mysite/mypage2.html 0 0
/mysite/mypage1.html 0 0
/mysite/ 6 0
Done
<!--NeedCopy-->
Example 4
In the following command, the pattern used is * *
. The appliance displays one set of collective statistics for all the requests received, with no row title.
> stat stream identifier myidentifier * *
Stream Session statistics
Req BandW RspTime Conn
18 5141 6 0
Done
<!--NeedCopy-->
Example 5
In the following command, the pattern is /mysite/mypage1.html *. The appliance displays one set of collective statistics for all the requests received for the URL /mysite/mypage1.html, with no row title.
> stat stream identifier myidentifier /mysite/mypage1.html *
Stream Session statistics
Req BandW RspTime Conn
15 30 0 0
Done
<!--NeedCopy-->
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.