Make Your Logs Work for You

The days of logging in to servers and manually viewing log files are over. SolarWinds® Papertrail™ aggregates logs from applications, devices, and platforms to a central location.

View Technology Info

FEATURED TECHNOLOGY

Kubenetes Cluster Logging Kubernetes Logging AWS Log Management GC Log Analyzer AWS Logging Docker Logging Docker Syslog Heroku Logging Logging Tools for Azure App

Troubleshoot Fast and Enjoy It

SolarWinds® Papertrail™ provides cloud-based log management that seamlessly aggregates logs from applications, servers, network devices, services, platforms, and much more.

View Capabilities Info

FEATURED CAPABILITIES

Log Viewer Firewall Log Analyzer Centralized Log Management Log Analysis Tail Logging Cron Job Monitoring Log Aggregator Cloud Logging

Aggregate and Search Any Log

SolarWinds® Papertrail™ provides lightning-fast search, live tail, flexible system groups, team-wide access, and integration with popular communications platforms like PagerDuty and Slack to help you quickly track down customer problems, debug app requests, or troubleshoot slow database queries.

View Languages Info

FEATURED LANGUAGES

Linux Logging Software Linux Log Management Ruby Logging Manager Golang Logging HAproxy Log Analyzer MySQL Logging NGINX Logging Javascript Logging Tomcat Logging Apache Log Analyzer

Administrator Guide
- Documentation for Papertrail
Collect Logs
Collect Logs: Apps & Services
Collect Logs: Hosting Services
Collect Logs: Integrations
- Fluentd
- Librato
- Amazon CloudWatch
- StatHat
- Amazon SNS
- HostedGraphite
- Datadog
- Zapier
- VictorOps
- New Relic traces
- Slack
- Campfire
- PagerDuty
- New Relic Insights
- Pushover
- AppOptics
- Geckoboard
- OpsGenie
- Honeybadger
Manage Logs
Send Logs for Analytics
SolarWinds Users & Orgs
Support and Security
- Security and Compliance
- Support Policy
What's New
- Papertrail Release Notes

Cloud 66

Introduction

Cloud 66 is a DevOps-as-a-Service for Rails, Node, and Docker. The instructions below focus on Rails; Node apps will have a similar setup, but may require some adjustment.

Setup

Create a Papertrail account (free)

If you don’t already have an account, sign up (free).

Set up deploy hooks

Download the template configuration files from the linked Gist to a .cloud66 deployment folder that’s located in the root of your source code.
Ensure that the latest release of remote_syslog2 will be deployed by modifying the version number contained within the download URL.

Provide the host and port details

Edit log_files.yml and provide the account-specific Papertrail host and port number, as shown under Log Destinations.

Deploy to Cloud 66

Cloud 66 will automatically read the contents of the .cloud66 directory and apply the details configured above.

Customization

Log files

The remote_syslog.init.d file by default grabs all the log files in the directory where Cloud 66 stores logs. To add additional files, modify EXTRAOPTIONS (if environment variables are needed to specify file locations) or provide a files: section in log_files.yml with absolute paths.

Deploy hooks

The default deploy hooks run on servers of any target type, and accomplish two key tasks:

Install remote_syslog2 (once, on build)
Copy and prepare the configuration and service files for remote_syslog2 (every deploy)

These hooks can be adjusted to meet the needs of the particular stack, as long as those two objectives are accomplished. For example:

Some stacks may not require regular updates to remote_syslog2 configuration, so certain steps could be moved to build_only.
Replacing the port number in the YML with the -p command line option and an environment variable in EXTRAOPTIONS to specify the Papertrail port might be desirable if the app is deployed from a public repo, since port details are account-specific and should not be committed to public repos.

Cloud 66’s deploy hook documentation.
Stuck? Feel free to contact us; we like helping.