The goal of monitoring is to provide a record of activities and performance statistics for various elements of the application. Monitoring is an ongoing administration task.
Use monitoring information to identify errors in the system and resolve them appropriately. This data can also be shared by platform and domain administrators by exporting and saving the data to a .CSV or .XML file.
To enable monitoring, platform administrators must set up a monitoring database, configure a monitoring data source or create a new one, and set up monitoring database flush and purge options. By default the installer created a monitoring database, however you can use another one if you choose.
To control monitoring, platform administrators create monitoring profiles and configurations, which define the targets (domains and packages) to monitor for a configured length of time. A default monitoring profile is created for you by the installer. Monitoring data can be deleted by the platform administrator as needed.
| Task | Frequency | Accomplished by |
|---|---|---|
| Create and enable monitoring profiles | One-time initial configuration with infrequent tuning as required | Sybase Control Center for Unwired Platform with the Monitoring node |
| Enable domain logging | One-time setup with infrequent configuration changes, usually as issues arise | Sybase Control Center for Unwired Platform with the node. |
| Review current/historical/performance metrics | Routine | Sybase Control Center for Unwired Platform with the Monitoring node |
| Identify performance issues | Active | Sybase Control Center for Unwired Platform with the Monitoring node |
| Monitor application and user activity to check for irregularities | Active | Sybase Control Center for Unwired Platform with the Monitoring node |
| Troubleshoot irregularities | Infrequent | Reviewing various platform logs |
| Purge or export data | On demand | Sybase Control Center for Unwired Platform with the Monitoring node |