# Variables on troubleshooting-router-error-responses: the opening and the
# sections General debugging steps, Levels and Gorouter error
# classification table (the excerpt the sites convert).
# Fields, separated by tabs: section, place, text, note (see checks/vars.py)
-	p	Are your 502 errors the result of your infrastructure, Cloud Foundry, or an app?	L7 app_runtime_abbr: the page's first sentence
debugging-steps	undefined	gather_routing_logs	L29: not defined; the published page shows nothing
debugging-steps	li	Gather the Gorouter logs and Diego Cell logs at the time of the incident.	L29: the list item around the undefined variable
debugging-steps	a	metrics	L40 gorouter_metrics_link: link text of a Markdown link whose URL is a variable
debugging-steps	a@href	running/all_metrics.html#routing	L40 gorouter_metrics_link: a variable as a Markdown link URL, in a nested list (the book makes it /running/all_metrics.html#routing)
levels	td	Gorouter cannot bind to its TCP port, a Cloud Foundry component has published invalid data to Gorouter.	L60 app_runtime_abbr: text in an HTML table cell
gorouter-error-classification	td	See Router Error: 502 Bad Gateway.	L388 gorouter_metrics_link: the cell around the link
gorouter-error-classification	a@href	../running/all_metrics.html#routing	L388 gorouter_metrics_link: a variable as an HTML href, in a table cell
