Forward logs from Render (Papertrail)
You can forward logs from Render services and datastores to Papertrail using Render log streams.
How it works
-
Your Render services and datastores produce logs.
-
Render forwards those logs to the configured logging provider.
-
Papertrail receives the logs through a TLS-encrypted TCP syslog connection.
-
Render formats syslog messages according to RFC 5424 and includes service metadata, such as the service slug, service type, and instance identifier.
Render does not emit logs for static sites. By default, a workspace log stream applies to supported services in the workspace. Pro workspaces and higher can override the default for individual services.
Prerequisites
-
An ingestion token for your Papertrail account.
To get a destination and token in Papertrail, add a new log destination. The ingestion token is generated along with the destination. Use the collector endpoints for your account's region:
-
Syslog (TLS):
syslog.collector.<REGION>.cloud.solarwinds.com:6514
Replace
<REGION>with the data center your organization uses:na-01,eu-01, orap-01. -
-
The provider's TLS syslog endpoint.
-
Access to the Render workspace and permission to configure Observability integrations.
Setup
For the Render-side instructions, see the Render documentation for Streaming Render service logs to SolarWinds.
Step 1: Get the provider endpoint and token
Use the TLS syslog endpoint and ingestion token for the account where you want to receive the logs.
-
Papertrail: Add a new log destination in Papertrail, and copy the token.
For Papertrail accounts using the SolarWinds collector, the format for the syslog endpoint is syslog.collector.<REGION>.cloud.solarwinds.com:6514. (Replace <REGION> with the region used by your account.
Step 2: Configure the Render log stream
-
Open your workspace in the Render dashboard.
-
Navigate to Integrations > Observability.
-
In the Log streams section, under Default destination, click Set default.
-
Enter the provider's TLS syslog endpoint in Log endpoint.
-
Enter the provider's ingestion token in Token.
-
Click Save changes.
Optionally, you can enable Include logs from preview instances to forward logs from service previews and preview environments.
Step 3: Configure individual services, if needed
Pro workspaces and higher can override the workspace default for individual services. Under the service's Settings page, go to Log stream, choose Override, and then select either a different destination or Don't forward this service's logs. A different destination requires a Scale workspace or higher.
Verify ingestion
After saving the configuration, generate a log message from a supported Render service. Confirm that the log appears in your Papertrail account shortly after Render starts forwarding it.
Render's syslog stream uses TLS-encrypted TCP and RFC 5424 formatting. Render also adds the service slug, service type, and instance identifier to each log line, which can help identify the source in the destination.
Remove or reset the configuration
To stop forwarding logs for an individual service, open the service's Settings page, go to Log stream, choose Override, and select Don't forward this service's logs.
To remove an individual-service override and return to the workspace default, click Reset to default.
To stop forwarding logs for the workspace, edit the default log stream under Integrations > Observability > Log streams, and remove or replace the destination.
The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.