Systems Monitoring 编辑

To ensure optimal uptime for app access and connectivity, you should monitor the following core components in the XenMobile environment.

XenMobile server

XenMobile server generates and stores logs on local storage that you can also export to a systems log (syslogs) server. You can configure log settings to specify size constraints, log level, or you can create custom loggers to filter specific events. You can look at XenMobile server logs from the XenMobile console at any time. You can also export information in the logs via the syslog server to your production Splunk logging servers.

The following list describes the different types of log files available in XenMobile:

Debug log file: Contains debug level information about core web services of XenMobile, including error messages and server-related actions.

Message format:

<date> <timestamp> <loglevel> <class name (including the package)> - <id> <log message>

  • where <id> is a unique identifier like sessionID.
  • where <log message> is the message supplied by the application.

Admin audit log file: Contains audit information about activity on the XenMobile console.

Note:

The same format is used for both admin audit and user audit logs.

Message format:

With the exception of required Date and Timestamp values, all other attributes are optional. Optional fields are represented with “ “ in the message.

<date> <timestamp> "<username/id>" "<sessionid>" "<deviceid>" "<clientip>" "<action>" "<status>" "<application name>" "<app user id>" "<user agent>" "<details>"

The following table lists the available admin audit log events:

Admin Audit Log Messages for eventsStatus
Loginsuccess/failure
Logoutsuccess/failure
Get adminsuccess/failure
Update adminsuccess/failure
Get applicationsuccess/failure
Add applicationsuccess/failure
Update applicationsuccess/failure
Delete applicationsuccess/failure
Bind applicationsuccess/failure
Unbind applicationsuccess/failure
Disable applicationsuccess/failure
Enable applicationsuccess/failure
Get categorysuccess/failure
Add categorysuccess/failure
Update categorysuccess/failure
Delete categorysuccess/failure
Add certificatesuccess/failure
Delete certificatesuccess/failure
Active certificatesuccess/failure
CSR certificatesuccess/failure
Export certificatesuccess/failure
Delete certificate chainsuccess/failure
Add certificate chainsuccess/failure
Get connectorsuccess/failure
Add connectorsuccess/failure
Delete connectorsuccess/failure
Update connectorsuccess/failure
Get devicesuccess/failure
Lock devicesuccess/failure
Unlock devicesuccess/failure
Wipe devicesuccess/failure
Unwipe devicesuccess/failure
Delete devicesuccess/failure
Get rolesuccess/failure
Add rolesuccess/failure
Update rolesuccess/failure
Delete rolesuccess/failure
Bind rolesuccess/failure
Unbind rolesuccess/failure
Update config settingssuccess/failure
Update workflow emailsuccess/failure
Add workflowsuccess/failure
Delete workflowsuccess/failure
Add Active Directorysuccess/failure
Update Active Directorysuccess/failure
Add masteruserlistsuccess/failure
Update masteruserlistsuccess/failure
Update DNSsuccess/failure
Update Networksuccess/failure
Update log serversuccess/failure
Transfer log from log serversuccess/failure
Update syslogsuccess/failure
Update receiver updatessuccess/failure
Update time serversuccess/failure
Update trustsuccess/failure
Add service recordsuccess/failure
Update service recordsuccess/failure
Update receiver emailsuccess/failure
Upload patchsuccess/failure
Import snapshotsuccess/failure
Fetch app store app detailssuccess/failure
Update MDMsuccess/failure
Delete MDMsuccess/failure
Add HDXsuccess/failure
Update HDXsuccess/failure
Delete HDXsuccess/failure
Add Brandingsuccess/failure
Delete Brandingsuccess/failure
Update SSL offloadsuccess/failure
Add account propertysuccess/failure
Delete account propertysuccess/failure
Update account propertysuccess/failure
Add beaconsuccess/failure

User audit log file: Contains information related to the user activity from enrolled devices.

Note:

The same format is used for both user audit and admin audit logs.

Message format:

With the exception of required Date and Timestamp values, all other attributes are optional. Optional fields are represented with “ “ in the message. For example,

<date> <timestamp> " <username/id>" "<sessionid>" "<deviceid>" "<clientip>" "<action>" "<status>" " <application name>" "<app user id>" "<user agent>" "<details>"

The following table lists the available user audit log events:

User Audit Log Messages for eventsStatus
Loginsuccess/failure
Session time-outsuccess/failure
Subscribesuccess/failure
Unsubscribesuccess/failure
Pre-launchsuccess/failure
AGEE SSOsuccess/failure
SAML Token for Citrix Filessuccess/failure
Device registrationsuccess/failure
Device checklock/wipe
Device updatesuccess/failure
Token refreshsuccess/failure
Secret savedsuccess/failure
Secret retrievedsuccess/failure
User initiated change passwordsuccess/failure
Mobile client downloadsuccess/failure
Logoutsuccess/failure
Discovery Servicesuccess/failure
Endpoint Servicesuccess/failure
MDM FunctionsStatus
REGHIVEsuccess/failure
Cab inventorysuccess/failure
Cabsuccess/failure
Cab auto installsuccess/failure
Cab shell installsuccess/failure
Cab create foldersuccess/failure
Cab file getsuccess/failure
File create foldersuccess/failure
File getsuccess/failure
File sentsuccess/failure
Script create foldersuccess/failure
Script getsuccess/failure
Script sentsuccess/failure
Script shell executionsuccess/failure
Script auto executionsuccess/failure
APK inventorysuccess/failure
APKsuccess/failure
APK shell installsuccess/failure
APK auto installsuccess/failure
APK create foldersuccess/failure
APK file getsuccess/failure
APK Appsuccess/failure
EXT Appsuccess/failure
List getsuccess/failure
List sentsuccess/failure
Locate devicesuccess/failure
CFGsuccess/failure
Unlocksuccess/failure
SharePoint wipesuccess/failure
SharePoint Configurationsuccess/failure
Remove profilesuccess/failure
Remove applicationsuccess/failure
Remove unmanaged applicationsuccess/failure
Remove unmanaged profilesuccess/failure
IPA Appsuccess/failure
EXT Appsuccess/failure
Apply redemption codesuccess/failure
Apply settingssuccess/failure
Enable tracking devicesuccess/failure
App management policysuccess/failure
SD card wipesuccess/failure
Encrypted email attachmentsuccess/failure
Brandingsuccess/failure
Secure browsersuccess/failure
Container browsersuccess/failure
Container unlocksuccess/failure
Container password resetsuccess/failure
AG client auth credssuccess/failure

Citrix ADC also monitors the XenMobile web service state, which is configured with intelligent monitoring probes to simulate HTTP requests to each XenMobile server cluster node. The probes determine whether the service is online and then respond based on the response received. In the event that a node does not respond as expected, Citrix ADC marks the server as down. In addition, Citrix ADC takes the node out of the load-balancing pool and logs the event for use in generating alerts through the Citrix ADC monitoring solution.

You can also use standard hypervisor monitoring tools to monitor the XenMobile virtual machines and to provide relevant alerts regarding CPU, memory, and storage utilization metrics.

SQL Server and database

SQL Server and database performance directly affects XenMobile services. The XenMobile instance requires access to the database at all times and goes offline (for example, stops responding) in the event of an outage to the SQL infrastructure. The XenMobile console may continue to function for a while following any disk space issues with SQL Server. To ensure maximum database uptime and adequate performance for the XenMobile workload, you should proactively monitor the state of your SQL Servers. For more information on monitoring your SQL Servers, see Monitoring and Tuning for Performance Overview. Additionally, you should adjust resource allocation for CPU, memory, and storage to guarantee service level agreements as your XenMobile environment continues to grow.

Citrix ADC

Citrix ADC provides the ability to log metrics to internal storage or to send logs to an external logging server. You can configure the syslog server to export Citrix ADC logs to your production Splunk logging servers. The following logging levels are available in Citrix ADC:

  • Emergency
  • Alert
  • Critical
  • Error
  • Warning
  • Information

The log files are also stored in Citrix ADC storage in the /var/log/ns.log directory and named newnslog. Citrix ADC rolls over and compresses the files by using the GZIP algorithm. Log file names are newnslog.xx.gz, where xx represents a running number.

Citrix ADC also supports SNMP traps and alerts as a monitoring option. For a list of SNMP traps, see SNMP monitoring.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据

词条统计

浏览:76 次

字数:17563

最后编辑:7 年前

编辑次数:0 次

    我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
    原文