Skip Navigation

Monitor 
NDS

This section lists the 
NDS
 services, resources, and performance data that you need to monitor. See the 
Microsoft Windows
 Server “Monitor Resource Usage (System Monitor)” guidelines at the 
Microsoft
 website.
Monitor the following services:
  • IIS
  • AtHocDeliveryService (Windows)
  • Plug-in-related services such as ATS for 
    TAS
  • SQL Server (instance name)
  • SQL Server browser
  • SQL Server agent
  • Third-party systems such as UCM
Monitor the following resources:
  • CPU usage
  • Memory usage
  • Disk usage
  • Network
  • Load balancing
Monitor performance counters:
The 
NDS
 performance counters are in the  
AtHoc
 Delivery group.
NDS performance counters in the Performance Monitor
  • TTSServicerunningState
    : If 
    TAS
     is hosted by 
    NDS
    , indicates the running status of the text-to-speech (TTS) service. Values:
    • Running=1
    • Stopped=0; in this state, all calls will fail
  • Loop Alert Init/Sec
    : Indicates how quickly alert messages are being processed.
    The ideal value is 2. If the value is 0, there are performance issues.
    • If the value is 0 for more than 5 minutes, the 
      NDS
       platform is not processing alert messages.
    • If the value is 0 for 1 minute, the system is slow. Check the other monitoring counters to identify other problems.
  • Loop Delivery Execution/sec
    : Indicates whether the 
    NDS
     platform is processing tasks.
    The ideal value is 2. If the value is 0, there are processing issues.
    • If the value is 0 for more than 5 minutes, the 
      NDS
       platform is not processing individual tasks.
    • If the value is 0 for 1 minute, the system is slow. Check the other monitoring counters to identify other problems.
  • NDS
     Delivery Lifecycle Monitoring: Contact 
    BlackBerry AtHoc
     customer support to set up this monitoring job.
    The life cycle monitor job provides status codes for each alert (task) delivered by 
    NDS
     and the plug-ins.