Jump to: navigation, search

Stat Server Timestamps

Stat Server internally maintains timestamps for multiple purposes:

  • To indicate when Stat Server received event notifications from T-Server, Interaction Server, Outbound Contact Server (OCS), or Configuration Server.
    Tip

    There is no direct connection between Stat Server and Outbound Contact Server—T-Server transmits OCS events to Stat Server through communication DNs.

  • To indicate when T-Server, Interaction Server, OCS, or Configuration Server sent event notifications to Stat Server.
  • To track the durations of actions.
  • To determine whether and when to clear stuck calls.
  • To profile a reporting interval.
  • To define time ranges over which actions should be measured.

This chapter focuses on the aspects of time that impact the statistical values Stat Server—in regular mode—reports to clients as the aspects relate to the generation of actions and the measurement of time-sensitive statistics. This discussion can help you decide which value to set for the UseSourceTimeStamps option of a stat type’s definition (described in the Stat Type Configuration Options table). For Stat Server applications that operate in restricted cluster mode (SSc), Stat Server inherently behaves as if the UseSourceTimeStamps option were set to yes. There is no option to configure SSc to use any other behavior; hence, the UseSourceTimeStamps option is obsolete for clustered applications.

This chapter contains the following sections:

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on June 16, 2015, at 09:56.