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
mid.server.xxx , 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. |