ECC Queue performance metrics

  • Release version: Australia
  • Updated May 20, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of ECC Queue performance metrics

    The ECC Queue performance metrics provide a snapshot of the communication between a ServiceNow instance and its MID Server through the External Communication Channel (ECC) Queue. These metrics help you monitor the message flow and processing load on the MID Server, enabling efficient troubleshooting and performance optimization within the ServiceNow AI Platform®.

    Show full answer Show less

    Key Metrics

    • ECC Queue message count (Input): Counts the number of input messages per queue agent (external system) currently in ready or processing states.
    • ECC Queue message count (Output): Tracks the number of output messages per queue agent in ready or processing states.
    • Avg waiting time (Input): Measures the average age of input messages in the ready state, indicating MID Server load and potential message pickup delays.
    • Avg waiting time (Output): Measures the average age of output messages in the ready state, similarly indicating MID Server load.
    • Processed message delta (Input): Shows the change in the count of input messages processed within the last 5 minutes, per queue agent.
    • Processed message delta (Output): Shows the change in the count of output messages processed within the last 5 minutes, per queue agent.

    Important Considerations

    The MID Server status reflected in these metrics does not directly indicate whether the MID Server service is running or stopped. Instead, it reflects the communication health between the MID Server and the ServiceNow instance, based on ECC Queue inputs.

    The MID Server status may show as down if there are issues such as:

    • Incorrect MID Server configuration (e.g., invalid credentials, wrong instance URL, or proxy misconfiguration).
    • Network communication blockage, such as firewalls or proxy restrictions.
    • The MID Server service being stopped manually or due to a crash.

    Practical Use for ServiceNow Customers

    By monitoring these ECC Queue metrics, you can identify communication bottlenecks and MID Server load issues, enabling proactive maintenance and ensuring smooth integration between your ServiceNow instance and external systems. This leads to improved reliability and performance of integrations relying on the MID Server.

    The metrics provide the ECC Queue performance snapshot within the ServiceNow AI Platform®.

    ECC Queue Metrics

    ECC Queue message count (Input)
    The External Communication Channel (ECC) Queue is a connection point between an instance and the MID Server. This metrics represent the count of input messages by respective queue agent name that is, name of the external system when it is in ready or processing state.
    ECC Queue message count (Output)
    The External Communication Channel (ECC) Queue is a connection point between an instance and the MID Server. This metrics represent the count of output messages by respective queue agent name that is, name of the external system when it is in ready or processing state.
    Avg waiting time (Input)
    This metric represents the average age for input message at ready state. This will tell us the load on mid server, since the messages are not picked up by mid server for processing.
    Avg waiting time (Output)
    This metric represents the average age for output message at ready state. This will tell us the load on mid server since the messages are not picked up by mid server for processing.
    Processed message delta (Input)
    This represents the delta change in the number of input messages that are in "processed" state since the previous data collection point (that is, in the previous 5 minutes) by respective queue agent name.
    Processed message delta (Output)
    This represents the delta change in the number of output messages that are in "processed" state since the previous data collection point (that is, in the previous 5 minutes) by respective queue agent name.
    Note:
    The MID Server status is not an indication of whether the MID Server service is running or stopped. Rather, the MID Server status is a representation of the communication between the MID Server and the instance. The MID Server status is decided based on the ecc_queue record inputs received by the instance from a MID Server. The MID Server status may be set to down if:
    • The MID Server configuration file has incorrect configuration such as invalid credentials, incorrect instance URL, or misconfigured proxy information.
    • The communication from the MID Server to the instance is being blocked, which could be due to a proxy or a firewall.
    • The MID Server service is not running, which could be caused by a manual stop or a crash of the MID Server service.