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.
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 key can be used within 5 minutes of an execution to see log
To enable network-level logging, you simply append
debug=true to the YQL
console URL or API query like this:
You can access network-level logs within 5 minutes of running a YQL statement or call.
You can view the logs using the YQL Console or using the YQL log URL with the query string parameter
id. We will discuss the
id attribute and then show how to view logs in the following sections.
When you make a request to the YQL Web Service and add the query string parameters
diagnostics=true&debug=true, the response will contain diagnostic information that can be used for debugging. In the returned diagnostic information
(shown below), you will see a
url element that has the
id attribute we mentioned earlier.
id is associated with a log message and is required to view log messages. We will be showing you how to use the
id in the next two sections to view logs from the YQL Console and using the YQL Log API.
For both community and built-in tables, if the env parameter is included in the YQL Web Service URL, the id attribute will not be returned in the response. When using community tables, to have the id attribute returned in the response, you must instead include the table with a USE statement.
idattribute of the
urlelement in the diagnostic information.
debug=true&diagnostics=trueto one of the YQL Web service URLs.
idkey provided in the
urlelement of the diagnostics information and append it to the YQL log URL as shown here: