Protocols, options and logging scenarios

SmartInspect's advanced protocols allow you to log to files, over TCP or via
named-pipes. Benefit from encrypted log files, backlog queues and a lot more.

SmartInspect can be used in many scenarios and comes with various flexible logging protocols. The following illustrations highlight some of the possible logging configurations.

Log Files

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.

Log Files
  • Rich binary log files for analysis with the SmartInspect Console
  • Text log files for inspection by end-users
  • Strongly encrypted log files to project your data
  • Flexible log file rotation for production systems
  • Tens of thousands of log entries per second

Live Logging

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.

Live Logging
  • Monitor applications in real-time with the SmartInspect Console
  • High-performance named pipe protocol for local live logging
  • TCP/IP protocol to monitor applications over a network
  • Highly flexible with synchronous and asynchronous logging options
  • Monitor production systems live without restarting them

SmartInspect Router

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.

Router
  • Receives logging data via TCP/IP and named pipes
  • High-performance log server for demanding production systems
  • Flexible rule-based logging to log files and other protocols
  • Support for logging from multiple processes to the same log file
  • Can be deployed to customers and production systems royalty-free

Memory Protocol

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.

Memory Protocol
  • Support for writing logging data to memory for best performance
  • Flush and write logging data to disk on application crash or other event
  • Ideal for production systems with high performance requirements
  • Has been designed for easy integration with exception reporting tools
  • Ability to attach log files to emails and crash reports