You can stream logs generated by your Render services to any logging provider with a TLS-enabled syslog endpoint.
When you add a log stream to your personal or team account, all supported services in that account start streaming their logs to the specified endpoint. For team accounts, this includes HTTP request logs for web services.
Each individual and team account is limited to a single log stream.
In the Render Dashboard, go to your Account Settings or Team Settings page.
Scroll down to the Log Streams section and click Add Log Stream. The following dialog appears:
Provide your syslog endpoint URL in the Log Endpoint field.
- Use the format
- For help finding the endpoint URL with common providers, see below.
- Use the format
If Render needs to include an authentication token with all reported logs, provide it in the Token field.
- This is required for logging providers that use a single syslog endpoint for multiple users, such as Datadog.
Click Add Log Stream.
You’re all set! Logs from Render will start to appear in your provider’s feed shortly.
Render streams logs to your provider’s syslog endpoint over TCP. Log lines are formatted according to RFC5424, which is supported by most popular providers.
Log streams do not support:
- Insecure (non TLS-enabled) endpoints
- Providers that require a custom log format
If you encounter issues integrating with a syslog-compatible provider, please let us know at firstname.lastname@example.org.
A formatted log line looks like this:
<0>1 2021-03-31T16:00:00-08:00 test-service cron-12345 74440 cron-12345 - hello this is a test
Render annotates each log line with:
- The corresponding service’s slug
- The type of service (
- A unique identifier for the instance
- Use this value to track your service between deploys, or to distinguish between multiple instances if you’re running more than one.
If you’re using a standard format like
json, Render maps the
level field to an appropriate syslog priority. Otherwise, Render makes a best effort to parse log levels, defaulting to
Consult your logging provider’s documentation to obtain your syslog endpoint and any necessary token. Instructions for certain providers are also available below.
If there’s a logging provider you’d like to see us add to this list, please submit a feature request.
Create a new source in Better Stack Logs with the platform
Then, when adding your log stream in Render:
in.logs.betterstack.com:6514as the Log Endpoint.
- Provide the source token from Better Stack as the Token.
For more information, see the Better Stack documentation.
See this section.
To stream logs to your existing highlight.io project:
syslog.highlight.io:34302as the Log Endpoint.
- Provide your highlight project ID as the Token.
- Your highlight project ID is shown in the top left of your project page.
For more information, see the highlight.io documentation.
We’ve observed high rates of connection failures with Mezmo’s syslog endpoint and do not recommend using them with Render at this time.
Log in to your Mezmo account and navigate to the sources page. Select syslog on the left sidebar to see your syslog endpoint.
Log in to your account and navigate to the setup page to find your Syslog endpoint:
If you use the same Papertrail account to collect logs from multiple providers, you can optionally generate a unique endpoint for your Render services.
Follow the instructions for configuring a cloud syslog source.
After you configure your source, Sumo Logic displays a modal with a Token and Host. Use these for your log stream’s Token and Log Endpoint, respectively.