Debugging Open Data Tables and YQL Network Calls
To aid in your debugging efforts, YQL provides the option to have network-level logging. When enabled, all network requests are uncached, so you can iteratively develop Open Data Tables more easily, as well as debug network requests between YQL and the remote service. Network logs display both the request headers and the response content for each network call.
Note
Network capture stops once YQL encounters a default (built-in) table or table fetched from yql.storage, even if subsequent requests are made using an Open Data Table.
When you enable network-level logging, YQL provides a key within the
diagnostics element for each network call that occurs, seen in the following YQL
response snippet as id attributes:
The id key can be used within 5 minutes of an execution to see log
data.
Enabling Logging
To enable network-level logging, you simply append debug=true to the YQL
console URL or API query like this:
http://query.yahooapis.com/v1/yql?q=select%20*%20from%20social.profile
%20where%20guid%3Dme&format=xml&env=http%3A%2F%2Fdatatables.org%2Falltables.env&debug=true
Viewing Logs
You can access network-level logs within 5 minutes of running a YQL statement or call. Simply append the id key provided in diagnostics to the following URL:
http://query.yahooapis.com/v1/logging/dump?id=
Example:
http://query.yahooapis.com/v1/logging/dump?id=5b81e4c4-11eb-43a5-866b-b1217498843e