• New Feature
  • Status: Closed
  • 2 Major
  • Resolution: Fixed
  • eellis
  • Reporter: jhartley
  • January 05, 2007
  • 0
  • Watchers: 0
  • July 27, 2012
  • February 15, 2007


The intent of this is primarily to assist support. The intent is to wrap up the details of collecting (and knowing) all of the relevant information into a single script. The output of this script is all the debugging information required by support personnel to assist in resolving an issue.

Requirements: * In the event of an exception with the Terracotta software, there should be a tool (usable for both L1 and L2 environments) to capture Terracotta instance data: * user environment variables (this information is stored in the tc-logs) * terracotta logs (client or server) * terracotta logs * stack traces etc. (these are printed to the logs) * Full mode * includes the heap also (or other large objects as deemed required) - specifically, this refers to the L2 database files * compressed into a single file archive (a zip)


Taylor Gautier 2007-01-17

Additional requirement

* We must explicitly define the set of environment variables we *will* send. We cannot implement sending environment settings by filtering out those which we do not want to send (such as username). This will ensure that we only send information that is relevant, and not accidentally include sensitive information.

Eric Ellis 2007-01-23

The primary application is complete. Certain tc-config log features won’t be tested CDV-93. In light of this I am unable to assure the behavior of the program.

Eric Ellis 2007-01-23

Do you still want me to package this as a standalone jar. If so there will be some config related code taken from the standard TC codebase. We may also want to integrate this standalone build into our buildsystem.

Steve Harris 2007-01-23

taylor is on vaca. It can probably wait till he gets back.

Eric Ellis 2007-02-15

Program is complete w/ unit test. After review with PM minor updates have been made. This should be correct according to the specs and feedback I’ve been given.

Eric Ellis 2007-02-19

I’ve written a unit test which iterates through every combination of inout/output variables that I could come up with. Valid and invalid. This feature should require very little manual testing.