---
title: "From Fragmented Logs to Full-Stack Visibility with SolarWinds Papertrail"
description: "Heroku applications combine dynos, databases, third-party APIs, and user interactions, making fragmented logs, metrics, and dashboards costly to correlate during production incidents. The expanded SolarWinds Papertrail add-on addresses this “swivel-chair” workflow by unifying real-time log management, metrics dashboards, and alerting in one interface. It supports live tailing and contextual search through the web, CLI, or API, while ingesting native Heroku metrics for dyno CPU, memory, load averages, application throughput, response times, error rates, and database performance. Custom thresholds based on minimum, maximum, average, or summary values can filter transient-noise alerts, with notifications sent to Slack, PagerDuty, and Microsoft Teams. The post’s incident example correlates a response-time spike with R14 “Out of Memory” errors from Dyno worker.1, identifying an oversized batch job; Librato and AppOptics were deprecated at the end of January 2026."
---

# From Fragmented Logs to Full-Stack Visibility with SolarWinds Papertrail

[Heroku](https://yomu.fyi/company/heroku) · Rachel Revoy · Mar 12, 2026

**Type:** Announcement

## Summary

Heroku applications combine dynos, databases, third-party APIs, and user interactions, making fragmented logs, metrics, and dashboards costly to correlate during production incidents. The expanded SolarWinds Papertrail add-on addresses this “swivel-chair” workflow by unifying real-time log management, metrics dashboards, and alerting in one interface. It supports live tailing and contextual search through the web, CLI, or API, while ingesting native Heroku metrics for dyno CPU, memory, load averages, application throughput, response times, error rates, and database performance. Custom thresholds based on minimum, maximum, average, or summary values can filter transient-noise alerts, with notifications sent to Slack, PagerDuty, and Microsoft Teams. The post’s incident example correlates a response-time spike with R14 “Out of Memory” errors from Dyno worker.1, identifying an oversized batch job; Librato and AppOptics were deprecated at the end of January 2026.

## Context

Heroku applications generate logs and metrics across dynos, databases, third-party APIs, and user interactions. Separating those signals across source code, deployment logs, monitoring dashboards, and alerting tools creates context switching, correlation blindness, alert fatigue, and tool sprawl during production troubleshooting.

## Approach / What changed

The expanded SolarWinds Papertrail add-on combines real-time log management, native Heroku metrics, dashboards, custom threshold alerting, and integrations with Slack, PagerDuty, Microsoft Teams, and other tools. Shared saved searches and alerts also provide a reusable library of team diagnostic knowledge.

## Takeaways

- SolarWinds Papertrail can display live logs alongside dyno, application, and database metrics, including CPU, memory, response times, error rates, connections, cache hit rates, and IOPS.
- Metric alerts support minimum, maximum, average, or summary thresholds; an example triggers when average error rate exceeds 5% over a five-minute window.
- The incident example links high response time to R14 “Out of Memory” errors from Dyno worker.1, leading to a batch-job optimization fix; Librato and AppOptics were deprecated at the end of January 2026.

**Tags:** [Heroku](https://yomu.fyi/topic/heroku), [Monitoring](https://yomu.fyi/topic/monitoring), [Observability](https://yomu.fyi/topic/observability)

- Source: [Heroku](https://www.heroku.com/blog/fragmented-logs-to-full-stack-visibility-solarwinds-papertrail)
- Source URL: https://www.heroku.com/blog/fragmented-logs-to-full-stack-visibility-solarwinds-papertrail
- Ingested by Yomu: 2026-09-10T04:05:23.352Z

[Read original post](https://www.heroku.com/blog/fragmented-logs-to-full-stack-visibility-solarwinds-papertrail)