Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

The MID Server ECC Queue

Log in to subscribe to topics and get notified when content changes.

The MID Server ECC Queue

The External Communication Channel (ECC) Queue is a connection point between an instance and the MID Server. Jobs that the MID Server needs to perform are saved in this queue until the MID Server is ready to handle them.

The MID Server subscribes to messages published by the Asynchronous Message Bus (AMB), which notifies the MID Server that it has pending tasks in the ECC Queue. If a job exists in the ECC Queue for that MID Server, the MID Server sets the status to "I'm working on it." When finished working on a requested job, the MID Server reports back to the ECC queue with the results.

You can access the ECC Queue by navigating any of these paths:
  • Discovery > Output and Artifacts > ECC Queue
  • Discovery > Discovery Schedules > {schedule name} > {Discovery status record}
  • ECC > Queue
  • {Discovery Status record} > ECC Queue

ECC Queue fields

An ECC Queue provides the following information:
Field Input value
Agent The name of the external system that this messages is either from or to. If the message is from or to a MID Server, the agent name is in the form, where xxx is the name of a particular MID Server.
Topic The name of the probe the MID server ran. If you are using a pattern for discovery, the Horizontal Pattern probeHorizontal Pattern probe appears.
Name The actual command the probe ran. For example, if Topic is SSHCommand, then the Name field contains the actual shell command to run. If you are using a pattern for discovery, the following appears:

Pattern Launcher: followed by the name of the pattern and the multipage number.

Source The IP address that the discovery is to run against. A few probes run against multiple IP addresses; in those cases, this field contains a human-readable description.
Response to This optional field contains a reference (sys_id) to the ECC Queue message that this message is in response to. Discovery makes extensive use of this field to track the hierarchy of messages that result from a given scheduled Discovery. Click the record icon for the value in this field to open the ECC Queue record for the activity that spawned the current probe or sensor record.
Queue An indicator of whether this message was is an input message or an output message.
State The state of the current ECC queue record. States update automatically.
Processed The time when this message was processed.
Created The time when this message was created.
Sequence The unique sequence number for this message. This value is automatically generated when an ECC Queue record is inserted. Its use is deprecated.
Error string An error message, if an error occurred during processing. This field is hidden on the standard form unless there was an error.
Payload The body of the message in XML format. The returned XML has a root tag of <results> containing one or more <result> tags and a single <parameters> tag. The parameters are simply an echo of those sent to the MID server in the probe; they vary from probe to probe, but in general they tell the probe the details of what it is to do and how it should behave. The result tags are the most interesting ones: they contain the actual data generated by the probe.

ECC queue controls

The ECC Queue form contains these related links:
Related link Description
Run again Runs the probe again. You can re-run probes when you encounter a failed discovery or other unexpected results.
Go to CMDB item Open the CI record for the CI that was updated during the discovery.
Go to Sensor Open the record for the associated sensor.