A New Log Explorer and HTTP Logs
This week we shipped two new logging capabilities for quickly diagnosing and debugging service issues:
- A new Log Explorer with text search, label-based filters, and jump-to-context
- Automatic HTTP request logs for all web services belonging to team accounts
Revamped log explorerThe new log explorer is available from your service's Logs page in the Render Dashboard: Search your logs for an arbitrary string (like a function name or user ID), filter by supported labels (like
level), and limit results to any time range within your account's retention period.
When you identify a line of interest, mouse over it and click its View in context button to open a new tab that shows the line in its original position. This gives you a clear, chronological picture of what was going on right when an error occurred.
Head over to your dashboard and give the new Log Explorer a try!
HTTP request logsWe now automatically generate HTTP request logs for web services belonging to team accounts. These logs appear alongside your application logs in the Log Explorer—see the lines starting with
You'll notice that HTTP request logs include a
requestID value, such as
74f98356-6f57-48a5. This uniquely identifies a request sent to Render from the public internet. Render sends this same value to your service and in its response to the requesting client—in both cases via the
Rndr-Id HTTP header:
If your service extracts this ID from the header and includes it in all logs related to a particular request, you can search for that ID in the log explorer to trace a request's full execution!
Log reporting example: DatadogIf your team has set up a log stream, Render now also forwards HTTP request logs to your third-party provider. This lets you set up advanced metrics reporting for your Render web traffic. As an example, if you're streaming logs to Datadog, here are some quick steps for visualizing your HTTP request data:
- In Datadog, select Logs > Generate Metrics:
- Click + New Metric.
Give the new metric a descriptive name (like
render_http_request_logs), then set the query to
Under group by, select one or more log fields to compare in your visualization. Depending on what you want to visualize, we recommend a combination of these:
@syslog.hostname(this value is the ID of your Render service)
- Click Create metric.
- From your metrics summary page, click the See in metric explorer button next to your new metric. Now you can view HTTP request data broken down by status code, host, or any other characteristics you've selected!