CMon Application Monitor & Exception Manager: Benefits, Features, and Functions

1. CMon Application Monitor & Exception Manager

2. If I use CMon what benefits do I get? • You can fix the application bugs easily. • Fixing the errors in a short time creates customer satisfaction. • You have the chance of upgrading your application in terms of performance and stability. • It helps development, test and service departments to detect the application problems without spending effort. • CMon saves you time and money.

3. What can I do with CMon ? • You can manage all of your application Exceptions. • You can monitor user actions on the application. • You can observe general application performance and detect leaks. • You can get information about the user screen usage.

4. What do you mean by saying “You can manage all of your application exceptions” ? • CMon logs all the exceptions even if you dont have any try catch statement. • You can observe the exceptions historically by using CMon web console. • CMon draws statistical diagrams regarding class and methods by means of this, you can decide the classes and methods that are causing the exceptions according to their exception counts. • It is possible to sort the result table ascending and descending.

5. What kind of data CMon collects when an exception occurs ? • Exception time. • Exception class,method & line. • Exception long description. • Source code presentation of exception : CMons makes the color of exception line lighter in the source code. • Source code analyzer : CMon displays the class source and lets the user jump between classes and methods.This enables the person who has the ability of code reader to use CMon as a software development IDE.

6. Clear case versions : Clear case version system is supported by CMon.It is possible to observe the last 5 versions of the classes in which the exception is thrown, you can switch to any class even if there is no exception to view the clear case data. Developer name,status,check in date, version number and comment belonging to the classes can be observed.

7. Execution flow :When an exception is raised it is possible to trace the stack to view the class and methods with the execution line. • Global Variables :When an exception is raised in a class, CMon displays the global variables and objects with their values.It is also possible to see object tree with the values. • Method Variables :The runtime data belonging to the method in which the exception is raised is displayed by means of CMon as it is in global variables.

8. Application Errors • Exception table : you can observe exception basic informations daily.You can make search in the exceptions.Exception time,class,method,line,screen and description information is available in this screen.

9. Exception Details: You can view the exception time,class,method,line and description as it is in the exception table, moreover,it is possible to observe the exception class clear case history information line version,date,event kind, developer name, developer comment for the change and version status.In addition to this, you can observe the exception line colored in the source code with the values of exception line objects.Source code last modified date and file size is also available to check the working version on the production environment.

10. Source Code Analyzer :On this screen, you can observe the method in which the exception is thrown, the source class information like clearcase history data,date and size information is also available.It is possible to jump to any source class that is working on the production environment by using the links.The source code can be analyzed in order to identify the exception case.

11. Execution Flow & Global Variables: It is possible to observe the exception stack trace in other words, methods orders with execution line before and after to exception point.On the other hand,global variables in the class definition are also available, as you see on the screen the global variables and object tree values can be analyzed like inspecting the objects in the debug mode.

12. Method Variables : When the exception is thrown in a method, CMon collects runtime data in the method.You can see the object and variable values on this screen. You can analyze the runtime data in order to decide the cause of the exception, it is like debugging the exception in the development environment.

13. Exception Class Statistics: You can view the classes that produced exceptions between the dates that you selected.Also, you can compare the classes according to produced exception counts.This helps you to decide the classes that cause the exceptions mostly.

14. Exception Method Statistics: You can view the methods belonging to class that produced exceptions between the dates that you selected.Also, you can compare the methods according to produced exception counts.This helps you to decide the methods that cause the exceptions mostly.

15. What do you mean by saying “You can monitor user actions on the application” ? • When an end user trigger an event on the application such as click on a button. CMon monitors the code execution. • You can observe all the classes and methods execution between user request and server response regarding the execution order. • You can view the executed lines in the classes, you can progress on the executed lines as if you are debugging the class. • This is very helpful If there is no error in the system but something works wrong it is possible to debug the executed lines so that which part of the code is executed. • Class and method execution performance can be displayed by CMon. • You can even see the execution performance in miliseconds between the class lines in the methods.

16. You can view the source code between the lines regarding the execution performance. • CMon helps you to detect the leaks in the application by observing the piece of code that causing the slow performance. Also you can view the method execution order in the class. • It is possible to view the class runtime object size by using CMon, this is important if there is a heap size dump in the system, at this time you may observe the total class runtime object size. • If there is no error in the system, and you wish to see the runtime class data in the application you can monitor any user events and can see the formed data during the method execution process. • By using CMon web console you can view the total time in miliseconds between the user request and server response and you can compare the requests. • It is possible to sort the result table ascending and descending.

17. Action Monitoring • Action monitoring table : you can observe user monitoring basic informations daily.You can vie w user name, ip adress, request start time, response end time, execution time in miliseconds and user request link information is available in this screen.

18. Action monitoring details: You can view monitoring details on this screen. Look at the executed classes between user request and server response.You can also observe the runtime object data size collected in these classes.In case you click on the link view class data you will see the runtime data belonging to related class, likewise, if you click on the view executed lines link, you will see the lines executed in the class.

19. Class runtime data: If you click on the view class data link on the user monitoring detail screen you will see this screen.As you see, Global variable values and class objects are avaiable to view the containing data.The objects can be viewed as if you are inpecting them on the debug mode at the development environment.

20. Class runtime executed lines: If you click on the view executed lines link on the user monitoring detail screen you will see this screen.You can view the executed lines in different color and you can progress forward and backward by using control buttons and you can even animate the execution process, you feel that as if you are at the development environment and debugging the class.

21. User monitoring request performance: If you click on the performance link on the user monitoring screen you will see this screen.As you can see the executed classes and methods between user request and server response are listed with the execution time in miliseconds.If you click on any class you will see the executed methods belonging to the class you have just clicked with the execution order view the execution time and decide where the request spend most of its time.

22. User monitoring request performance: If you click on the the method you will see the executed lines in the method. Look at the executed lines and the executed time in milisecods between the lines.You can see the method total execution time and line by line execution time, It is very easy for you to detect the method lines where the execution slows down.

23. User monitoring request performance: Click on the view code link and see the piece of code between the lines.This will help you observe the application leak where the code makes the application run slowly.You wont have to spend too much time to detect the leak.This kind of performance problems cannot be resolved in the development environment you will need to production environment conditions. CMon will help you to observe where the code cause performance problem.

24. What do you mean by saying “You can observe general application performance and detect leaks” ? • You can observe the total application performance for those who are defined to be monitored. • It is possible to view the class usage count and average execution time for the application users. • You can also view methods that are belonging to any class as it is like class viewing you can observe methods usage counts and total average time. • You can also view usage count and performance of the code lines belonging to any method. • If you wish, you can see the source code executed between any code lines. • It is possible to sort the result table ascending and descending.

25. Application Performance • Application performance class table : you can observe class usage and execution time performance daily.At the right bottom, total class execution time and user request count average is displayed.

26. Application performance methods: You can view method usage count and average execution time on this screen,At the right bottom, total method usage and average execution time of all methods are displayed.

27. Application performance method lines: You can view method lines usage count and average execution time between start and end line on this screen,At the right bottom total line usage count and average execution time is displayed.

28. Application performance method lines source code : You can view source code between start and end line of method execution. At this point you can view the code block that causes the application run slowly.

29. What do you mean by saying “You can get information about the user screen usage” ? • You can observe the users who are using application screens with their ip addresses. • You can view usage graphics for users. • You can view usage graphics for screens. • You can view the graphic of screens that are used by any user. • You can view the graphic of users who use any screen. • You can filter the user & screen usage results according to users,ip addresses and screens. • It is possible to sort the result table ascending and descending.

30. Screen Usage • User screen usage table: All the user events on the screens are logged and displayed.This action doesnt reduce the application performance.On this screen you can view the user & screen usage.

31. User frequency: This is the user application usage frequency you can view how many times a user clicked on the screen and make a comparision between them.

32. User screen relation: On this screen you can observe the actions of any user on any screen.

33. Screen frequency: This is the screen usage frequency you can view how many times a screen is used and make a comparision between them.

34. Screen user relation: On this screen you can observe the user actions performed on any screen.

35. Screen ip relation: On this screen you can observe the actions performed by the specific ip address on any screen.

36. Configuration Screen • You can make all the application configuration on the settings screen which is not accessible by any user, only admin users can view and change the settings. • The configuration tips and further information is explained on the same screen. • You can make a very detailed configuration, almost every thing in the CMon is configurable. • On the next screen you can view a sample configuration.

37. Application Configuraton