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
Create an Amazon Web Services account at http://aws.amazon.com and activate Amazon S3 on your account. Once your account is activated, create a bucket for log archives, and share write-only access to Papertrail for nightly uploads.
After setting up S3 archiving it takes approximately 6-7 hours for logs to be available in the archive.
Create a new bucket for your log archives in your S3 account, using the information below. See Creating, configuring, and working with Amazon S3 buckets in the Amazon documentation for more information.
companyname-papertrail. The name should consist of only lowercase letters, numbers, and hyphens. (more info).
4b0a516d33d6b490d119301a4b16db3fa49a6b33bdc5135c2ab90e8184f6995fwith Write access enabled for Objects. To set up permissions with IAM instead, see Define Sharing Policy with IAM.
Changes can be made after the fact by selecting the bucket and choosing the Permissions tab.
After submission, Amazon’s management console will change the user name to
aws. This is expected.
Amazon also has instructions for editing bucket permissions.
If you followed the instructions above to grant permissions via the AWS Management Console, skip this step.
If you prefer defining a bucket policy to control access, here’s an example policy that permits Papertrail to upload archives:
bucket-name/papertrail/logs/ is the directory for Papertrail. The
s3:DeleteObject action isn’t strictly necessary – it’s only used to clean up the temporary
test_file.txt during initial configuration. (However, since
s3:PutObject also permits overwrites, denying
s3:DeleteObject doesn’t provide any significant protection.)
Under Settings > Archives, enable S3 archive copies and provide the S3 bucket name.
Papertrail will perform a test upload as part of saving the bucket name (and will then delete the test file). Note that a new bucket can sometimes take several hours to become available, due to DNS propagation delays. If it fails, wait two hours, and try again.
When archives are uploaded to the bucket, each file is named under the path (key prefix) provided to Papertrail, typically
<xxx> is an ID. For example, an archive file for 3 PM UTC created on February 25, 2019 would be:
Days are from midnight to midnight UTC.
Papertrail supports S3 rather than Glacier because:
Yes, Papertrail takes advantage of S3’s server-side encryption so that archived data is encrypted at rest using AES-256.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.