Show Hide

 

Feedback

  • Contents
 

Revisions

This topic summarizes changes in Log Viewer.

PureConnect 2018 R3

No changes.

CIC 2016 R1

Updated to reflect new branding and the transition from Interaction Client .NET Edition to Interaction Desktop.

CIC 2015 R1

Updated documentation to reflect changes required in the transition from version 4.0 SU# to CIC 2015 R1, such as updates to product version numbers, system requirements, installation procedures, references to Interactive Intelligence Product Information site URLs, and copyright and trademark information.

IC 4.0 Service Update 5

Note that when tracing levels are modified in Interaction Administrator for specific users, the tracing change is not reflected in Trace Config utility on the user’s workstation. This is a display issue only. Opening up the log does reflect the change.

IC 4.0 Service Update 4

No documentation revisions.

IC 4.0 Service Update 3

The StatServer sub-system (StatServerU.exe) was split into two binaries that replaced StatServerU.exe in the \I3\IC\Server\ folder on the IC server. The old log file (StatServer.ininlog) was also deprecated and replaced by new logs:

  • StatServerAgent[U|UD].exe handles agent related statistics.  Its log file is statserveragent.ininlog

  • StatServerWorkgroup[U|UD].exe handles workgroup related statistics. Its log file is statserverworkgroup.ininlog.

The split enhances processing power and allows for statistics gathering in larger environments with higher call rates.

IC 4.0 Service Update 2

A journal file is now created to track log start/stop times. When dealing with a subsystem that produces large log files, it can be difficult to know which logs contain entries for a specific time range. To make this task easier, an additional file is created per subsystem to denote when instances of the subsystem start and stop.

All ininlog files now have a single 'journal' file that is maintained in parallel with the logs. There is only one journal for a log, no matter how many times a subsystem starts and stops, and regardless of whether it runs simultaneously more than once.

For log files like TSServer.ininlog, TSServer_1, and so on,, the journal file is named TSServer.ininlog_journal. It contains a timestamp for each entry and log when a log file is created and when it is closed. This file can be used to determine which log file contains a particular timestamp range you're interested in.

IC 4.0 Service Update 1

No documentation revisions.

IC 4.0 GA

  • The IC User Apps install now adds shortcuts for starting inintraceconfig and ininlogviewer from the Start Menu > Programs > Interactive Intelligence folder.

  • If you're looking at a log and hit "refresh", you may not see new messages immediately, since trace messages are buffered. You can optionally disable buffering by setting the ININ_TRACE_BUFFERSIZE environment variable to 0.

  • Log Viewer has a new 'profiler' feature, based on enter and exit scope tracing.  With a log file open, select Profile from the Tools menu to get output similar to:

    Each column is sortable. You can optionally right-click an entry to jump to that function’s longest execution Scope Entry line in the logfile.  One limitation is that you cannot have any filters applied to the logfile when running the profiler.  The profile functionality will work with a Global Time Range Filter set, but it will not work with named/adhoc filters.

  • Updated the procedure titled Grant permission to run IC System Manager for user interface changes in Interaction Administrator.

  • Updated Filter Criterion dialog to cover options that apply ad-hoc or named filters.

  • Updated explanation of the Bookmarks dialog to cover new import/export options.

  • Removed references to versions of IC prior to 4.0 as distinctions between IC 2.x and IC 3.x no longer apply.

  • Updated screen cap of the About dialog to show Log Viewer's current version number.