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
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
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
Meet the Event Viewer
It's the heart of Papertrail.Start Tour
TAKE A TOUR
TBD - APM Integration Title
TBD - APM Integration DescriptionTBD Link
APM Integration Feature List
TBD - Built for Collaboration Title
TBD - Built for Collaboration DescriptionTBD Link
Built for Collaboration Feature List
Collect Logs: Apps & Services
Collect Logs: Hosting Services
Collect Logs: Integrations
Send Logs for Analytics
SolarWinds Users & Orgs
Support and Security
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.
If you don’t already have an account, sign up (free).
.cloud66deployment folder that’s located in the root of your source code.
Cloud 66 will automatically read the contents of the
.cloud66 directory and apply the details configured above.
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.
The default deploy hooks run on servers of any
target type, and accomplish two key tasks:
These hooks can be adjusted to meet the needs of the particular stack, as long as those two objectives are accomplished. For example:
-pcommand line option and an environment variable in
EXTRAOPTIONSto 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.