How to debug origin timeouts and errors? Follow
Section Console provides various tools to help you debug your origin.
At the top of the Overview page for your application's environment, if there is an origin issue you will see similar warnings to below.
The text explains the there are timeouts when connecting to the origin, and that this is happening outside of the Section platform.
When inside the Section admin console you can click on View More Details and it will deep-link to the Kibana business intelligence tool which will give details logs on the issue.
There have been 4 timeouts when trying to connect to your origin server in the last 10 minutesThese errors are outside Section's system. This is not something Section can address, and we suggest you investigate your server or contact your hosting / development partner.
View more details
The second message explains that there are 5xx status codes coming from the origin to Section, and again these errors are outside of the Section platform.
There have been 5 errors due to the origin server closing the connection in the last 10 minutesThese errors are outside Section's system. This is not something Section can address, and we suggest you investigate your server or contact your hosting / development partner.
Section Console Overview Page https://www.section.io/docs/explanations/section/monitoring/
Application > Grafana > Traffic Summary
You can then click on the Grafana Panel View, next to the pull-down arrow, and click through to a full-page view of Status.
Now in the full-page view, you can get a larger graph with which you can scale in or out, change the date range, click on a status to filter, etc.
Monitoring Grafana https://www.section.io/docs/tutorials/monitoring/grafana/
Kibana is a powerful business intelligence tool that Section uses for reporting, visualization, and querying.
Section Console > Application > Environment > Real-Time > HTTP Logs
To check for 5xx errors at origin click on HTTP Logs and the Open in New Window button.
Use this search query to begin
status:[500 TO 599] AND _type:last_proxy-access-log
From this report, get a section_io_id b163c399c1f659fbf62bcfcc41b9eb25 and use that to trace a single request.
Tracing a single request, and using Section's edge debug headers we can see section_origin_status is 502.
- Basic Logging: https://www.section.io/docs/how-tos/debugging/basic-logging/
- Debugging a Slow Site: https://www.section.io/docs/how-tos/debugging/debug-slow-website/
- Debug Headers: https://www.section.io/docs/reference/debug-headers/
- HTTP Error Messages: https://www.section.io/docs/debugging/reference/http-error-messages/