Jump to: navigation, search

Log Analysis

The Log Analysis console allows you to analyze Genesys application log files. You can open several log files and review key data points, such as ConnIDs, for a single call flow across application logs.

Available actions include:

  • Isolate call flows for a given connection ID (ConnID) or domain name (DN)
  • Graph a call flow across multiple log files
  • Identify all error or warning messages in a log file
  • Drill down on a specific event or message to see detailed information
  • Highlight any text in a log file and right-click to search the Genesys Knowledge Base for solutions related to that text
Important
Log Analysis is a resource-intensive functionality due to parsing of data. If the utilized memory in the Workbench Server host is approaching exhaustion, you will receive a notification on the bottom right of the Log Analysis browser window. Opening more files at this time may result in substantial performance degradation for all Workbench users.
  • You can click on the Clear Display (trash can) icon Trash can.png to purge all files currently open in Log Analysis and start a new session.
  • It can take some time to index and process a log file for analysis. While the file is being processed, you will see a “spinner” indicator.


Progress Spinner on Log Analysis Console

WB Log Analysis spinner.png

When the processing of a log file has completed, the Log Analysis console shows a list of events in that log file.

Log Events List in Log Analysis Console

WB Log Analysis events.png

Log Analysis Icons Menu

The Log Analysis screen has several icons you can use to analyze log files:

Log analysis icons menu.png

Click the “Select a file” icon File.png to open a single log file or an LFMT log package.

Click the “Select a folder” icon Folder.png to open a group of log files in a folder.

Click the Index icon Index.png to list all events for a key data point, such as a Connection ID (ConnID).

Click the Statistics icon Stats.png to view available statistics for the log files currently open in the Log Analysis console.

Click the Clear Display (trash can) icon Trash can.png to clear the log files currently loaded in the Log Analysis console, so you can review a new log or set of logs.

You can also click on any of the events listed in the top right pane, and the full log file is displayed in the bottom right pane, with the details for that log event highlighted in red. You might need to scroll down to see the red text.


Selected Log Event Highlighted in Red in Bottom Pane

WB Log Analysis red event.png


You can select a word or phrase in the log file details pane at the bottom right and right-click to search the Genesys Knowledge Base for troubleshooting information about that log event or error message.


Log Text Selected for Knowledge Base Search

WB Log Analysis Trigger KB Search.png


The My Support login screen will be displayed, and after you login, the Knowledge Base search results will be displayed:


Knowledge Search Results for Selected Log Text

350

Supported Log Types

The following Genesys application logs are currently supported in the Log Analysis console:

  • SIP Server component
  • T-Server components (for 8.1 supported T-Servers)
  • GVP Components:
    • CCP (Call Control Platform)
    • CTIC (CTI Connector)
    • MCP (Media Control Platform)
    • PSTN connector
    • Resource Manager

Events that are tracked and displayed in the Log Events row of the Event Correlation dialog include the following general errors from all supported components:

    • 404 Not Found
    • 405 Method Not Allowed
    • 480 Service Unavailable
    • 500 Server Internal error
    • And most other 400 & 500 range errors

Additionally, some specific errors from certain components are also captured and displayed as a Log Event.

  • Resource Manager
    • Unable to find physical resource for servicetype
    • RequestResource failed
    • Unable to allocate source resource %s
  • Media Control Platform
    • POST request failed due to unsupported URL
    • <event name="msml.conf.recording.failure" id=”*”/>
  • CTI Connector
    • Error: TMOperationNetworkDisconnect
    • Error: text="Result=FAILURE&reason=FeatureNotSupported"
This page was last modified on February 23, 2018, at 07:37.

Feedback

Comment on this article:

blog comments powered by Disqus