Event Logging
Increasing the log level for events on Siebel servers or components is a common practice and is well documented. Of course, this includes the notorious environment variables such as SIEBEL_LOG_EVENTS. Administrators have to be aware of the performance implications of these settings.
SQL Spooling
Apart from using the well-known /s switch with a stand-alone executable, we can also get the generated SQL from object managers and other server components. This is useful when we want to trace down database related performance problems.
E-mail Alerts
Introduced in Siebel 7.7, the Siebel Administrator Notification component uses specialized alert profiles to send e-mails when a component is in trouble.
SARM
There is one simple rule: "Turn SARM on!". The Siebel Application Response Measurement module provides an administrator with ample information about what is going on and how fast/sluggish it is going on.
Client-side logging
To monitor the browser-side performance (at least for High-Interactivity clients), we can enable client side logging.
Usage Collection
Another technique which is more into usage tracking is the Siebel Usage Collection module
_stats.swe
The _stats.swe page is a default mechanism of collecting simple statistics about the request performance between the Siebel Web Server Extension and the object managers. And it's a reported vulnerability if you don't turn it off (or rename the _stats.swe page) in public Siebel web apps.
No comments:
Post a Comment