Remote Targeting of SpyKer Event Traces via Distributed ArchitectureDebug, diagnose and optimize embedded system performance

Automatically collect trace data into buffers.
SpyKer dynamically extracts the traces and removes its probe points.

1. What is SpyKer?
2. What does a trace tool do?
3. No kernel rebooting or instrumentation required
4. Reading SpyKer event trace data
5. >>Remote targeting of event traces
6. Selective event tracing and buffering for crash analysis
7. SpyKer Pro PDF brochure (203 kB)

Key components in SpyKer™ communicate via TCP/IP, which allows for use over a LAN or the Internet.

This remote capability, combined with SpyKer's non-intrusiveness, enables SpyKer's auto-instrumentation module to be deployed in target systems for later use by developers in search of bugs and/or performance data during "real-world" sessions.

SpyKer also supports the ability to configure traces on the target system without the use of the SpyKer display tool. This is especially useful in cases where no connection is available between the host and target systems.

Java-based GUI for workstation compatibility

SpyKer's front-end graphic user interface (GUI) is written in Java™ and runs on any workstation equipped with a Java Virtual Machine (JVM). Hence the GUI can reside locally or remotely from the system to be measured.