SmartInspect can be used in many scenarios and comes with various flexible logging protocols. The following illustrations highlight some of the possible logging configurations.
SmartInspect supports three configurable log file formats for every need. The rich binary log file format can be analyzed with the powerful SmartInspect Console. The text file protocol on the other hand allows end-users to open log files and identify configuration problems with your application. The third option, strongly encrypted log files, is perfect for protecting your sensitive and proprietary information.
To monitor an application in real-time, either locally or over the network, SmartInspect offers high-performance named-pipes and TCP/IP logging protocols. Using these protocols together with the SmartInspect Console allows you to monitor and analyze production and development systems while they are running.
The SmartInspect Router service application is ideal for debugging and monitoring complex production systems. It can receive logging data via TCP/IP and named pipes from multiple applications and machines and write it to log files. Because the SmartInspect Router can be configured with custom rules, it is possible to merge logging data from different processes or machines into a single log file.
One of SmartInspect's unique features is the ability to log to memory and only write the logging data to disk when your application crashes. This can either be accomplished with the SmartInspect memory protocol or with the backlog protocol option. This is ideal for production systems and when the performance at run-time has the highest priority. The memory protocol is also the perfect choice for integrating SmartInspect with exception report tools.