-
-
Importing and synchronizing StyleBooks from GitHub repository
-
Simplified migration of NetScaler application configuration using StyleBooks
-
Create and use custom StyleBooks
-
Create a StyleBook to upload SSL certificate and certificate key files to NetScaler ADM
-
Enable analytics and configure alarms on a virtual server defined in a StyleBook
-
Migrate configuration pack of a StyleBook to another StyleBook
-
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!
Enable analytics and configure alarms on a virtual server defined in a StyleBook
You can use the operations construct to configure NetScaler ADM analytics to collect appflow records on all or some of the traffic transactions handled by any virtual server component that is part of a StyleBook. You can also use this construct to configure alarms to get insight into the traffic managed by the virtual server.
The following example shows an operations section of a StyleBook:
operations:
analytics:
-
name: lbvserver-ops
properties:
target: $components.basic-lb-comp.outputs.lbvserver
filter: HTTP.REQ.URL.CONTAINS("catalog")
-
alarms:
-
name: lbvserver-alarm
properties:
target: $outputs.lbvserver
email-profile: $parameters.emailprofile
sms-profile: "NetScalerSMS"
rules:
-
metric: "total_requests"
operator: "greaterthan"
value: 25
period-unit: $parameters.period
-
metric: "total_bytes"
operator: "lessthan"
value: 60
period-unit: "day"
<!--NeedCopy-->
The attributes in the analytics section are used to instruct NetScaler ADM analytics feature to collect appflow records on a virtual server component identified by the target property. You can also optionally specify a filter property that accepts a NetScaler policy expression to filter requests for which appflow records are collected on the virtual server.
When a configuration pack is created from this StyleBook, the NetScaler ADM analytics feature is configured to collect appflow records on the virtual servers that were specified when these are created in the process of creating a configuration pack.
The attributes in the alarms section are used to set thresholds to generate alarms and send notifications on the virtual server identified by the target property. In the above example, the email-profile and sms-profile properties are used to specify where the notifications should be sent. The rules section defines the thresholds. For example, if the total requests handled by the virtual server are greater than 25 and for a period defined by the user, an alarm is set and notification is sent. The “period-unit” specifies how frequently an alarm is triggered. It can take the value of the day, hour, or weekly.
You can use the following operators when comparing the metric value to the threshold value:
- “greaterthan” for “>”
- “lessthan” for “<”
- “greaterthanequal” for “>=”
- “lessthanequal” for “<=”
Note that StyleBooks use API names for the metrics and not the names displayed on the NetScaler ADM analytics GUI.
To learn how to view and analyze data collected on virtual servers that were created as part of a configuration pack, see the NetScaler ADM analytics documentation.
Share
Share
In this article
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.