-
-
-
View recommendations and manage your ADCs and applications efficiently
-
-
-
Events
-
Use ADM log messages for managing and monitoring your infrastructure
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!
Events
When the IP address of a Citrix Application Delivery Controller (ADC) instance is added to NetScaler Application Delivery Management (ADM), NetScaler ADM sends a NITRO call and implicitly adds itself as a trap destination for the instance to receive its traps or events.
Events represent occurrences of events or errors on a managed NetScaler instance. For example, when there is a system failure or change in configuration an event is generated and recorded on the NetScaler ADM server. Events received in NetScaler ADM are displayed on the Events Summary page (Infrastructure > Events), and all active events are displayed in the Event Messages page (Infrastructure > Events > Event Messages).
NetScaler ADM also checks the events generated on instances to form alarms of different severity levels. These alarms are then displayed as messages, some of which might require immediate attention. For example, system failure can be categorized as a “Critical” event severity and would need to be addressed immediately.
You can configure rules to monitor specific events. Rules make it easier to monitor the events, which can be many, generated across your NetScaler infrastructure.
You can filter a set of events by configuring rules with specific conditions and assigning actions to the rules. When the events generated meet the filter criteria in the rule, the action associated with the rule is run. The conditions for which you can create filters are: severity, NetScaler instances, category, failure objects, configuration commands, and messages.
You can also ensure multiple notifications are triggered for an event for a specific time interval, until the event is cleared. As an extra measure, you can customize your email with a specific subject line and user message, and upload an attachment.
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.