What is the XML feed?

The XML Feed is an XML formatted stream of data carrying monitoring information for a requested period for a Device, or a Task.

Where can I get basic info about the XML request process?
What is the basic XML FEED request?

The Basic XML FEED request is a specially formatted URL with a number of GET parameters, divided by “&” symbol, which you request by HTTPS protocol.

Content of the basic XML FEED URL is constructed from the following commands: 

 [base_service_address]  +  [unique_account_uid]  +  [Site_id]  +  [parameter1]+[parameter2]... 


 https://xmlreporter.dotcom-monitor.com/reporting/xml/responses.aspx  ?pid=4229AF4F0FB545AEA75EAF2013E51BB7  &Site=12345  &Type=Overall 

Additional Parameters’ description is available in the Using the XML Reporting Service (XRS) article.

How can I get a specific Device ID, or Task ID?

Open the target Device in the list to Edit. In the browser’s address bar you’ll see something like

https://user.dotcom-monitor.com/ClientID/DeviceEdit?pid=dc7f4ff2ca944dekjh1078b96707002& deviceId=63698 & taskId=132834 

The deviceId=63698 is the device ID.
The taskId=132834 is the task ID.

How can I see unique account identifier (UID)?

Account UID (aka Integration UID, Client UID) is a unique account identifier. Add it under Configure > Integrations > Integration UIDs.

Ok, how does this look in practice?

Therefore by going to Configure > Integrations > Integration UIDs …copy UID 123456789456123789456123, then insert where Xs for PID. And then go to Device Edit. Copy the device ID, e.g., 12345, from the URL, insert where Xs for Site:

What are NEW additional XML details on DNS etc..

The term we are using is “Extended XML details”, they include all underlying tree-of-response children i.e. list of all loaded elements. This option is available by adding the “Options=RequestDetails” parameter.

You can find how to enable  “Extended XML details” in the Using the XML Reporting Service (XRS) article.

How do I filter response by monitoring agent?

If you want the XML Feed to show results only from certain monitoring agents, add “&Location” string parameter to the request URL in the following way:

http://xmlreporter.dotcom-monitor.com/reporting/xml/responses.aspx?pid=XXXXXXXXXXX&Site=XXXXX&Type=Detail &Location=[agent1]&Location=[agent2]...&Location=[agent5] ...


http://xmlreporter.dotcom-monitor.com/reporting/xml/responses.aspx?pid=4229AF4F0FB545AER75EAF2013EB1BB7&Site=77895&Type=Detail&Location=MN, USA &Location=Amazon-US-East&Location=Frankfurt,Germany&Location=Sydney, AU 

List of agents’s strings values:


  • MN, USA
  • NY, USA
  • CA, USA
  • FL, USA
  • Montreal, Canada
  • CO, USA
  • TX, USA
  • VA, USA
  • Amazon-US-East
  • Buenos Aires, Argentina

  • London, UK
  • Frankfurt, Germany
  • Amsterdam, Netherlands
  • Tel-Aviv, Israel
Asia, Australia, Africa

  • Hong Kong, China
  • Sydney, AU
  • Amazon, Japan
  • Shanghai, China
  • South Africa
What are definitions for the responses fields?


<Name>Demo request</Name> 
<Monitoring-Date-Time>3/26/2014 12:38:38 PM</Monitoring-Date-Time> 
<Monitoring-Location>FL, USA</Monitoring-Location> 
  • Duration – Overall time taken to complete the task (Basically – sum of times below)
  • DnsTime – is the time required to resolve a host name (e.g. www.google.com) into a numeric IP address (e.g.
  • SSLTime – is the time required to complete the SSL handshake process.
  • ConnectionTime – is the time required to create a TCP connection to the web server (or proxy). Keep-Alive connections are often used to avoid the overhead of repeatedly connecting to the web server.
  • RequestTime – is the time required to send the HTTP request message to the server and will depend on the amount of data that is sent to the server. For example, long Send times will result from uploading files using an HTTP POST
  • FirstPacketTime – (Time To First Byte) time elapsed to start receiving data from the remote web server. In other words, the time between request and response first byte received.
  • DownloadTime – is the time taken to read the response message from the server. This value will depend on the size of the content returned, network bandwidth and whether HTTP compression was used. In other words, the time between response first and last bytes.