Friday, July 8, 2011

PTC System Monitor

Most of the developers/Administrators struggle to troubleshoot a problem within the system coming either from a badly configured sql queries or custom code. How about tracing a performance issue caused by a valid unknown sql query from Windchill (user defined reports or custom code)? The current monitoring system has limited capability to point the module/method/class/query which eating up maximum resources on the system causing system terribly slow. This is also possible in case of complex system configuration where time required for investigating the issue is huge.

During the PlanetPTC conference this year, PTC had major announcement by introducing a new module call PSM (PTC System Monitor) which will be shipped at no cost along with PTC Windchill Product after October 2011.

PSM is a separate server-client system powered by dynaTrace that monitors Windchill application. dynaTrace has emerged as the new leader in application performance management. Here are some silent features:

  1. Reduce Turnaround Time and Escalations: Based on the PTC Experience with this tool, it is estimated that the turnaround time to troubleshoot an issue with this tool will be 10 times faster than the current one.
  2. Easier Monitoring and Diagnosis: This tool is packed with multiple dashboards, incidents and alerts, built-in analysis tools. Runtime data can be cached and stored automatically. This is very useful in case of escalating call to PTC tech support where we need to exchange the information to the PTC. This tool allows us to automatically record Sessions and export to PTC support team.

PSM is a heavy weight server-client system which requires its own database to be configured. However it there is flexibility to configure the PSM system on remote machine other than the PTC Server.

PSM system is based on Agent, Sensors and Measures which are inserted logically within the Windchill system. Agent’s gathers monitoring (cpu, memory, threads) and diagnostic information (java stack, arguments, SQL statements, etc) to send to the collector. Sensors are Entry Points or measurement points into the Java stack. Sensors recognizes the java inheritance concept hence not all the classes required sensors. The specification for sensor is basically done by developers which allow PSM to monitor piece of code and its performance. PTC has already developed sensors for all the major API’s. If developer needs to put a sensor into code, the code has to inherit the sensor specification provided by tool so that the custom code can be monitored through PSM.

PSM is also capable of producing the reports which will briefly explain the overall health of the Windchill system. PSM stays on even if Windchill is down. This feature is interesting in terms of reducing the Admin efforts to manage/create the reports based on current system monitor tool.

Currently this tool is planned for Windchill platform. Based on interaction with PTC folks they are also planning for FlexPLM release; however I am not aware about the exact date. For Windchill tool will be available for Windchill 9.1 and 10.0 users after October 2011.

I am really impressed by this tool as this will help developers/Admins to reduce the time of investigation put on monitoring the system and trace to exact point from where the issue is coming. It has a visibility and insight into Windchill application. It also helps developers to optimize their development efforts to maximize the user experience and release product faster.