Following is a list of changes to SQL Anywhere Monitor introduced in version 12.0.0.
Changes to metric collection Previously you could configure the type of metrics that the Monitor collected and set the alert thresholds. Now you can only configure the alert thresholds. See SQL Anywhere Monitor.
Removing resources You can remove a monitored resource from the Monitor without stopping it. Previously you had to stop the resource before you could remove it. See Removing resources.
Resources no longer have states Now resources only have statuses. See Dashboards.
Changes to alert status When a condition that triggered an alert no longer exists, the alert status changes to Inactive. An alert with the status Inactive indicates that the condition that triggered the alert is no longer present, but a Monitor user has not manually resolved it. In addition, the Monitor assigns a severity to each alert that it issues. See Dashboards.
Changes to the alert threshold defaults Previously, the Monitor issued alerts when the CPU memory usage reached 85 percent of the maximum cache size for two contiguous collection intervals. Now, the default is 90 percent and the time threshold is 30 seconds. See Alert definitions and thresholds.
All users are required to log in into the Monitor Previously, the Monitor did not require anyone to log in to have read-only access. Now all users are required to log in to the Monitor. See Monitor users.
Changes to user language preferences When a user logs in, the Monitor uses the language preferences of that user to configure the language displayed in the Monitor and used in alerts. Previously, the Monitor used the language set in the browser. See Editing a Monitor user.
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|