Enable Logging

[stvhwrd]

HTTP Server will contribute four logs:

• DebugType
• ErrorEventType
• SystemEventType
• UserCommandType

DebugType

Debugging messages contain all the information of user commands, in addition to an optional debug message

• "timestamp": int // UNIX timestamp
• "server": string // name of server eg. "Transaction Server"
• "transactionNum": int // enumeration of transaction
• "command": string // one of the known commands ("BUY", "SELL" etc)
• "username": string // optional alphanumeric username
• "stockSymbol": string // optional three-char alphanumeric stock symbol ("NWC", "BTK")
• "filename": string // optional name of file to be written to
• "funds": decimal // optional dollars and cents (eg 24.99)
• "debugMessage": string // optional debug message or description

ErrorEventType

Error messages contain all the information of user commands, in addition to an optional error message

• "timestamp": int // UNIX timestamp
• "server": string // name of server eg. "Transaction Server"
• "transactionNum": int // enumeration of transaction
• "command": string // one of the known commands ("BUY", "SELL" etc)
• "username": string // optional alphanumeric username
• "stockSymbol": string // optional three-char alphanumeric stock symbol ("NWC", "BTK")
• "filename": string // optional name of file to be written to
• "funds": decimal // optional dollars and cents (eg 24.99)
• "errorMessage": string // optional error message or description

SystemEventType

System events can be current user commands, interserver communications, or the execution of previously set triggers

• "timestamp": int // UNIX timestamp
• "server": string // name of server eg. "Transaction Server"
• "transactionNum": int // enumeration of transaction
• "command": string // one of the known commands ("BUY", "SELL" etc)
• "username": string // optional alphanumeric username
• "stockSymbol": string // optional three-char alphanumeric stock symbol ("NWC", "BTK")
• "filename": string // optional name of file to be written to
• "funds": decimal // optional dollars and cents (eg 24.99)

UserCommandType

User commands come from the user command files or from manual entries in UI web forms

• "timestamp": int // UNIX timestamp
• "server": string // name of server eg. "Transaction Server"
• "transactionNum": int // enumeration of transaction
• "command": string // one of the known commands ("BUY", "SELL" etc)
• "username": string // optional alphanumeric username
• "stockSymbol": string // optional three-char alphanumeric stock symbol ("NWC", "BTK")
• "filename": string // optional name of file to be written to
• "funds": decimal // optional dollars and cents (eg 24.99)

[stvhwrd]

Since every log is tied to a transaction number and a command, should probably maintain one ~global~ appropriately scoped commonlib.LogCommandParameters instance per request

[qqqstuv]

Sorry I'm a bit unsured why should we keep track of LogCommandParameters per request? Isn't the webserver done with LogCommandParameters after it has sent off a message to logging server? Also afaik the workload generator currently does not send the transactionNumber to webserver. I need to enable that at some point, right?

[stvhwrd]

No need to enable that - the HTTP server now assigns transactionNum as the requests come in. We'll need to modify the parameters downstream to ensure that transactionNum propagates