Overview
The Chronon Recording Server allows you to use the Chronon Recorder on remote machines, and allows you to manage and share recordings easily within teams.
Benefits
- Record remote Java applications
The Recording Server makes it share recordings on different machines among team members or across multiple teams. - Control the Chronon recorder on remote machines easily
Every remote Java application running with a Chronon Recorder can be easily managed through a central web UI. You can manage the Chronon Recorder on an entire datacenter using the Recording Server. - Share recordings easily among team members
The Recording Server makes it share recordings on different machines among team members or across multiple teams. - Record long running programs that run for weeks or months
The Recording Server is specifically designed for long running, server side applications that run for weeks or months at a time. The Recording Server will take care of splitting the recording if it get too large and flushing out old recordings. - Rid yourself of log files
Get rid of the need to look at long sparsely detailed log files to debug your program. Just play back the entire execution and see exactly what took place in your program. Also, use the Post Execution Logging feature in the Chronon Time Travelling Debugger to add logging anywhere in your code *after* your program’s execution.
Features
- Dynamically Start and Stop Recording
The Recording Server allows you to dynamically start and stop the Chronon recorder in a running Java application. This way you can run your application always with the recorder enabled but in a dormant state, and record only when you need to, say at the first occurrence of a bug. - Automatically flush out old recordings
Old recordings are automatically flushed away to keep from filling up disk space. - Split recordings at time intervals for long running programs
For recording long running programs, you can configure time intervals to ‘split’ a recording. This makes sure that an individual recording doesn’t get too large physically. Also it allows you to easily pick at recording at a time interval you want to examine, say between 2pm and 3pm. - Easily configure and control the performance of Chronon Recorder
You can configure all aspects of the Chronon Recorder and easily control the performance impact it has on your program. - No extra network traffic
The Recording Server is designed to handle 1000s of nodes. There is no extra network traffic generated during operation. All recordings and recorder management activities take place locally on the box where the recorder is running, thus having zero impact on your network traffic. - Fault Tolerant Architecture
The Recording Server is designed with failure in mind. Even if one of the nodes goes down, or the machine hosting the recording server itself goes down, the recording and management of recordings on each node will continue without interruption.