Symptom Driven Diagnostics
Last updated
Last updated
Besides historical data analysis, Flopsar provides symptom driven diagnostics feature. To enable this feature, you need to subscribe to the online data service first by clicking the main options menu and selecting the Settings menu item.
When you subscribe to the service, you will be able to see online data.
You will need the View online data permission to be able to see the online view.
Each tile in the view represents some application. The application name is displayed at the top of the tile. The tile consists of four vertical bars and a central double graph. Tiles can be added to the view from the list of applications on the right side. If you want to add an application, you need to select the application in the list, drag and drop it on the tiles view. Tiles can be removed from the view by clicking the tile options menu and selecting the Remove menu item.
The central graph is composed of two graphs: threads and load. The Thread graph presents the total number of threads currently used in the application. The Load graph presents the total number of currently collected entry points.
The EXCEPTIONS bar presents information about the exceptions' density in entry points. In other words, it shows what percent of the collected entry points have thrown exceptions. The value in the center of the bar denotes the current number of entry points with exceptions.
The three-level bars present how many incomplete entry points are currently processed in the application. The levels are duration-based, which means every incomplete entry point goes to one of the levels based on its current duration. The levels duration thresholds are user-defined. To edit the levels, click the options menu in the selected application tile and select the Settings menu item.
In the levels edit form above, you can set the baseline thresholds for two levels. You need to specify the maximum time current incomplete entry points can take to stay in the corresponding level. In other words, if some entry point is still being executed, and its execution time so far is less than the first level threshold, then it will go to the first level. Each refresh time, this entry point's execution time is checked and if its duration exceeds the level's threshold it is moved to the next level. Finally, the entry point either completes or goes to the last level and stays there until it completes. Every entry point, whose execution time exceeds the second level threshold will go to the third level automatically, so there is no need to set the third level threshold. The values in the center of bars denote the number of incomplete entry points for each bar.
The online data is refreshed every 15 seconds.
Besides the visual representation of currently executing methods, there is the fault detection feature, which provides visual and audible notifications when a possible fault is detected. The are three sensitivity levels of the symptom trigger: low, medium and high. If you want to disable the feature, you must select the none option in the Symptom Trigger Sensitivity combo box.
Every fault is composed of events. The number of events depends on the selected fault sensitivity. There are two types of generated events: the duration based and the exception based. To view the fault list, you need to click the Symptom Log menu item in the option menu.
The Symptom Log contains a collection of all symptoms. There is a blue time axis with blue circles at the top. Each circle represents a symptom. To see the symptom events click one of the circles.
