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

EVENT VIEWER

APM INTEGRATION

BUILT FOR COLLABORATION

Meet the Event Viewer

It's the heart of Papertrail.

Start Tour

TAKE A TOUR

Live Tail Seek by Time Context Elegant Search APM Integration Skim-ability Saved Searches Log Velocity Analytics

TBD - APM Integration Title

TBD - APM Integration Description

TBD Link

APM Integration Feature List

Feature 1

TBD - Built for Collaboration Title

TBD - Built for Collaboration Description

TBD Link

Built for Collaboration Feature List

TIPS FROM THE TEAM

Tips from the Team

By engineers, for engineers

View More Tips

Additional Tips

Kubernetes Logging Monitoring WordPress Error Logs A Guide to Log Filtering Managing and Analyzing Firewall Logs What Your Router Logs Say About Your Network How to Diagnose App Issues Using Crash Logs Docker Container Logs 5 Reasons LaaS Is Essential for Modern Log Management 6 Secrets for Successful Log Management How to Live Tail Docker Log

Technical Resources

Admin Guide Getting Started Release Notes

Educational Resources

Take a Tour Tips from the Team Use Cases

Connect with Us

THWACK Community Blog COVID-19 Resource Center

Meet SolarWinds
Observability SaaS Logging Sign Up

Search Events

core-db-01.sjc sshd: Accepted publickey for samantha from 4.28.11.28 port 37884 ssh2
core-db-01.sjc sshd: pam_unix(sshd:session): session opened for user samantha by (ui
www2 tomcat.log: 16:47:40,446 INFO [web.scripts.AbstractRuntimeContainer] Initiali
haproxy epa-http.txt: mac6100.home.edu.yamaguchi-u.ac.jp [30:00:52:22] "GET /docs/ci
www2 tomcat.log: 16:47:40,868 INFO [web.site.FrameworkHelper] Successfully Initial
farm-trivia-72 app/web.1: method=GET path=/a/product format=html controller=rails_ad
farm-trivia-72 app/web.1: User Load (1.2ms) SELECT "users".* FROM
dyno=web.1 connect=1ms service=44ms status=200 bytes=6407
haproxy epa-http.txt: 202.96.29.111 [30:01:48:16] "GET /waisicons/text.xbm HTTP/1.0"
haproxy epa-http.txt: dd14-034.compuserve.com [30:01:48:22] "GET /Rules.html HTTP/1.
haproxy epa-http.txt: www-c8.proxy.aol.com [30:01:48:23] "GET /docs/Searchable.html
farm-trivia-72 app/web.1: method=GET path=/a/ format=html controller=rails_admin/mai
remote_ip=23.252.53.179 user_id=1 params={}
www1 tomcat.log: 17:32:59,713 INFO [web.scripts.DeclarativeRegistry] Registered 67
www2 tomcat.log: Aug 27, 2009 4:52:30 PM org.apache.coyote.http11.Http11BaseProtocol
www1 tomcat.log: 17:32:59,714 INFO [web.scripts.AbstractRuntimeContainer] Initiali
www1 tomcat.log: 17:33:59,965 INFO [web.scripts.DeclarativeRegistry] Registered 10
haproxy epa-http.txt: sfsp03.slip.net [30:00:46:11] "GET /docs/Access HTTP/1.0" 302
www1 tomcat.log: 17:33:59,965 INFO [web.scripts.AbstractRuntimeContainer] Initiali
www2 tomcat.log: INFO: Pausing Coyote HTTP/1.1 on http-8080
www2 tomcat.log: Aug 27, 2009 4:52:31 PM org.apache.catalina.core.StandardService st
haproxy epa-http.txt: sfsp03.slip.net [30:00:46:18] "GET /Access/ HTTP/1.0" 200 2376
farm-trivia-72 heroku/router: at=info method=GET path="/a/product?_pjax=%5Bdata-pjax
farm-trivia-72 app/web.1: Product Load (1.7ms) SELECT "products".* FROM "product
farm-trivia-72 app/web.1: User Load (1.2ms) SELECT "users".* FROM "users" WHERE
farm-trivia-72 app/web.1: (1.3ms) SELECT COUNT(*) FROM "products"

Context

SolarWinds Observability SaaS Logging shows links to see any message in context. Click the sender (orange) or program (blue) to jump to that message within the related stream. Click the plus sign (+) for additional context choices or to transition to the command-line.

If you haven’t tried context links yet, here’s 3 situations where they’ve helped us:

Infrastructure-wide history. While viewing a HTTP request log for a user-facing error, clicking access_log shows all Web requests. Because other Web servers are also searched and the query (like an IP address or user ID) is preserved, SolarWinds Observability SaaS Logging returns the end-to-end history.
Single-system impact. After spotting a kernel problem in a Unix syslog message, clicking the sender will show events from only that system.
Long events, like when a search matches one line in a multi-line exception. Click the log sender to see it all.

If you’re used to grep, we’ve tried to adopt the best parts of its context and jettison those that we didn’t use.

Elegant Search

Seek By Time