TeleFlow Logging

From TeleFlow

Revision as of 16:32, 8 October 2009 (edit) Chris (Talk | contribs) m (→For Problems @@@) ← Previous diff		Revision as of 16:58, 8 October 2009 (edit) (undo) Chris (Talk | contribs) Next diff →
Line 4:		Line 4:
	===When TeleFlow Server Logs===		===When TeleFlow Server Logs===
-	Typically, TeleFlow Server is configured such that it logs all application errors that occur while the TeleFlow Server service is running. @@@ options / how to @@@	+	Typically(by default), TeleFlow Server is configured such that it logs all application errors that occur while the TeleFlow Server service is running. There are a number of options that control how the logging works, as described in the sections that follow.
		+	Logs are named using a date/time stamp and the name of the line from the@@@
-	===Where TeleFlow Server Logs To===	+	====TeleFlow Config - Server-wide Log Settings====
-	You can check where your TeleFlow Server is logging by looking at the setting in TeleFlow Config (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow Config). Logs are written to the "Log Directory". (NOTE: The directory path must exist for TeleFlow to write to it.)	+	TeleFlow Config is accessible in the Windows Programs menu. (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow Config)
		+
		+	The settings in TeleFlow Config that affect how TeleFlow Server logging works are:
		+	* Log Directory: This is where logs are written. (NOTE: The directory path must exist for TeleFlow to write to it.)
		+	* Maximum Log File Size: The maximum size a daily application log is allowed to grow to before TeleFlow stops writing to it. This is ignored when the "Unlimited Log File Size" checkbox is checked.
		+	* Unlimited Log File Size: Logs can continue to grow to any size.
		+	* Log Lines: For application error logging only, this is the number of lines of log output the server will write for a single error.
		+
		+
		+	====TeleFlow LineList - Log Settings by Application Instance/Line====
		+
		+	TeleFlow LineList is accessible in the Windows Programs menu. (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow LineList )
		+
		+	The settings in TeleFlow LineList that affect how TeleFlow Server logging works are:
		+	* Name: This name, along with a date/time stamp,
		+	* Restart Count: This is the number of times the application should restart (when an error occurs) before it stops running. This setting is ignored when the "No limit" checkbox is checked.
		+	* No limit: Indicates the application should restart after errors an unlimited number of times.
		+	* Log output: There are two logging options for an application instance, as follows:
		+	** Errors only: Logs "Log Lines" (see TeleFlow Config, above) of output to the error log file when errors occur, and only when errors occur.
		+	** All events: Logs everything that happens while the server is running to the log.
		+	* Append to file: If checked, TeleFlow appends to the log whenever it is writing to it. This means, if there are multiple errors, for example, that all of them can be written to the log. Unchecked, the log will contain only the most recent error, or when logging all events, only what has happened since the last time the application was started.
		+
		+
		+	===Reviewing Logs For Errors===
		+
		+	If you know the application you are running @@@
Line 18:		Line 44:
	====For Problems That Result in Application Errors (Resulting in dropped calls)====		====For Problems That Result in Application Errors (Resulting in dropped calls)====
-	====For Non-Error Producing Problems (I.e. Application doesn't error, but doesn't work as expected)====	+	If you can't solve the problem you are l
		+	Gather all files in the TeleFlow log directory, zip them up, and either make them available for download, or email them to support
		+	(In TeleFlow Config
		+	====For Non-Error Producing Problems (I.e. Application doesn't error, but doesn't work as expected)====
		+	=====If Your Application Isn't in Production (or, on a development server)=====
		+	Open your active application list file in TeleFlow LineList, and make the following changes:
		+	(NOTE: If you don't know what the active list is, check here: @@@)
		+	* Set "Restart Count" = 0
		+	* Uncheck the "No limit" checkbox
		+	* Set "Log output" = "All Events"
		+	* Uncheck "Append to file"
		+	=====If You Can Only Test in Production=====
	In TeleFlow Config (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow Config):		In TeleFlow Config (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow Config):

---

Revision as of 16:58, 8 October 2009

This topic is intended to explain how TeleFlow Server (and TeleFlow Simulator) logging works, how to configure it to suit your needs, and how to read and take advantage of the logs.

Contents 1 When TeleFlow Server Logs 1.1 TeleFlow Config - Server-wide Log Settings 1.2 TeleFlow LineList - Log Settings by Application Instance/Line 2 Reviewing Logs For Errors 3 Collecting Logs for Support 3.1 For Problems That Result in Application Errors (Resulting in dropped calls) 3.2 For Non-Error Producing Problems (I.e. Application doesn't error, but doesn't work as expected) 3.2.1 If Your Application Isn't in Production (or, on a development server) 3.2.2 If You Can Only Test in Production

When TeleFlow Server Logs

Typically(by default), TeleFlow Server is configured such that it logs all application errors that occur while the TeleFlow Server service is running. There are a number of options that control how the logging works, as described in the sections that follow.

Logs are named using a date/time stamp and the name of the line from the@@@

TeleFlow Config - Server-wide Log Settings

TeleFlow Config is accessible in the Windows Programs menu. (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow Config)

The settings in TeleFlow Config that affect how TeleFlow Server logging works are:

• Log Directory: This is where logs are written. (NOTE: The directory path must exist for TeleFlow to write to it.)
• Maximum Log File Size: The maximum size a daily application log is allowed to grow to before TeleFlow stops writing to it. This is ignored when the "Unlimited Log File Size" checkbox is checked.
• Unlimited Log File Size: Logs can continue to grow to any size.
• Log Lines: For application error logging only, this is the number of lines of log output the server will write for a single error.

TeleFlow LineList - Log Settings by Application Instance/Line

TeleFlow LineList is accessible in the Windows Programs menu. (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow LineList )

The settings in TeleFlow LineList that affect how TeleFlow Server logging works are:

• Name: This name, along with a date/time stamp,
• Restart Count: This is the number of times the application should restart (when an error occurs) before it stops running. This setting is ignored when the "No limit" checkbox is checked.
• No limit: Indicates the application should restart after errors an unlimited number of times.
• Log output: There are two logging options for an application instance, as follows:
  • Errors only: Logs "Log Lines" (see TeleFlow Config, above) of output to the error log file when errors occur, and only when errors occur.
  • All events: Logs everything that happens while the server is running to the log.
• Append to file: If checked, TeleFlow appends to the log whenever it is writing to it. This means, if there are multiple errors, for example, that all of them can be written to the log. Unchecked, the log will contain only the most recent error, or when logging all events, only what has happened since the last time the application was started.

Reviewing Logs For Errors

If you know the application you are running @@@

Collecting Logs for Support

If you are attempting to collect and provide logs of a specific issue(s) in order to get support/help solving a problem, the following sections provide tips on the best/most effective methods of providing both enough of the logs to solve the problem with the minimum amount of unnecessary information:

For Problems That Result in Application Errors (Resulting in dropped calls)

If you can't solve the problem you are l Gather all files in the TeleFlow log directory, zip them up, and either make them available for download, or email them to support

(In TeleFlow Config

For Non-Error Producing Problems (I.e. Application doesn't error, but doesn't work as expected)

If Your Application Isn't in Production (or, on a development server)

Open your active application list file in TeleFlow LineList, and make the following changes: (NOTE: If you don't know what the active list is, check here: @@@)

• Set "Restart Count" = 0
• Uncheck the "No limit" checkbox
• Set "Log output" = "All Events"
• Uncheck "Append to file"

If You Can Only Test in Production

In TeleFlow Config (Start >> Programs >> TeleFlow >> Server Tools >> TeleFlow Config):

• Set "Active Application List File" to the Default.tal file verified/modified in TeleFlow LineList.
• Make sure "Log Directory" is a valid directory path.
• Check "Unlimited Log File Size".
• Set "Log Lines" to 2000.
• Check "Start TeleFlow Service Automatically".

Before restarting the computer, ensure the following:

• The log directory for TeleFlow is empty (clear any files in it).
• The services for the telephony hardware will start automatically with Windows.

Once the steps above are complete, restart the computer. After logging in:

• Wait a couple minutes before proceeding with the remaining steps.
• Verify that board services have started.
• Run TeleFlow Monitor to see if your applications are running with green lights, or if they have stopped with errors (red lights).

If the system has started with green lights, call the phone number to reach the system to see if it answers.

If it starts with red lights, review the logs. The logs should have only a single attempt to start the application and wait for an incoming call. This means the log will show the minimum amount of output with whatever error(s) are preventing the system from running normally.