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

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

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

TBD - APM Integration Title

TBD - APM Integration Description

TBD Link

APM Integration Feature List

TBD - Built for Collaboration Title

TBD - Built for Collaboration Description

TBD Link

Built for Collaboration Feature List

Join SolarWinds Day October 19 to see the next evolution in observability. Register now.

Blog > Archive file timestamp changes

Archive file timestamp changes

Posted by By telliott on May 7, 2012

Update Monday, May 21: These changes are now active.

Along with realtime search and tail, Papertrail generates daily or hourly log archive files. They downloadable from Papertrail’s site and optionally, uploaded to your own S3 bucket.

The current archive format has 2 flaws that we want to correct:

  • Zone: The timestamps are in PST8PDT. They should be in UTC.
  • Format: Although the current timestamps use a common format, ISO 8601 is at least as common and is more widely documented (RFC 3339). Nearly all languages include libraries to parse ISO 8601 timestamps.

For comparison, a current timestamp (PST): 2011-02-10 00:19:36 -0800

And the same local time in ISO 8601 (UTC): 2011-02-10T00:19:36Z

This change will affect archives created on or after Monday, May 21, 2012. The archive file for Sunday, May 20 may contain 16 hours of logs and Monday, May 21 may contain 32 hours.

Please open a support request if we can answer any questions or help modify a post-processing script.