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
Follow the steps in Alerts.
Provide the New Relic account ID. This is the number that appears after
/accounts/ in New Relic URLs.
Access Insights, then select Manage Data in the left sidebar and API Keys in the top bar. Either register an Insert API key by clicking the plus button next to Insert Keys, or select an existing Insert key to use with Papertrail. Enter the key in Insights Insert key.
Papertrail sends events to Insights using the HTTP API, and respects the Insights limits on event format and post size. The event type is
PapertrailAlert and the
search_name is the name of the search the alert is attached to.
Event attributes map, as much as is feasible, directly from Papertrail to Insights. To facilitate expected behavior of Insights events, the timestamp of the event in Insights and the Papertrail
received_at value (which are the same) are in UNIX epoch time, and the
source_id of the events are strings.