 |
 |
 |
 |
The AutoPilot Detector looks at the WebLogic run-time environment and detects issues. It then generates a report with the abnormalities detected.
When AutoPilot monitoring is ON for a WebLogic Server, AutoPilot automatically detects situations when WebLogic server is not able to process incoming Application requests and it runs detector and blackbox automatically. This helps find the abnormalities at the time when server is not responding. Detector report will in most cases point to the root cause of the hung WebLogic state.
Best of all, AutoPilot runs Detector automatically and saves the results in the database when it detects adverse conditions. At the same time detector can also be run at any particular time by WebLogic Administrators to find out any issues with the runtime of WebLogic and Application combination.
It is recommended to let AutoPilot monitor invoke the Detector at the time when server is in hung state. This way you get an experts analysis of the WebLogic State automatically. Detector uses the dynamic knowledge database built by Arcturus engineers with years of WebLogic experience. Since Detector looks at the runtime state of WebLogic server it is recommended to run Detector on a Server that has been running for some time. If you run Detector on a freshly started WebLogic server you may not get any results.
To run Detector:
Select AutoPilot WL > AutoPilot Detector > Run Detector from the tree in the left pane.
Select a server from the drop-down box that appears in the right pane.
Determine whether you want sensors to be automatically created from the time that you run Detector. Click Toggle to toggle Auto Sensors creation on and off, as indicated by the traffic light icon. When Auto Sensors Creation is on, data relating to each problem detected will be saved for analysis. You may want to turn Auto Sensors Creation off if Detector finds many problems with the server, since monitoring each one can consume a large amount of system resources.
When you have decided whether or not to apply Auto Sensors Creation to monitor the results, and have set the "Auto Sensors Creation Toggle" button accordingly, click Start AutoPilot Detector. Detector will then examine your WebLogic environment for run-time problems. When the detection process is complete, a message will display, notifying you that Detector has completed the process.
To view Detector results:
Click AutoPilot Detector > Show Detector Results.
Select the criteria pertaining to the areas you want to examine using the drop down boxes. These drop down boxes include:
Server
MBean Type
Name
Time Period
Date Range (Optional; used only when "Time Period" is set to "Custom" Otherwise, this option is disabled. See Step Three below.)
If you want to specify a specific Date Range, click the Custom Dates option from the Time Period drop-down. This allows you to click inside the From and To text boxes, displaying a calendar from which you can select the date range by clicking dates directly on the calendar.
The example report below is automatically generated by AutoPilot under slow database response condition simulation. As you can see from the report AutoPilot is able to determine connections pool utilization is maxed out, no database connections are available and wait time is going up. Also we can see from the report that many transactions are getting rolled back. This clearly tells us that database is becoming the problem area.
