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
rKubelog is a simple way to send logs from a Kubernetes (K8s) cluster to Papertrail without having to configure DaemonSets, sidecars, fluentd, or persistent claims. With rKubelog, it’s easy to use Papertrail for logging in nodeless clusters, such as EKS on Fargate, and is perfect for smaller, local development clusters to setup logging within seconds.
Logs can also be sent from a Kubernetes cluster using a SolarWinds Snap Agent installed on your host. Alternatively, you can manually configure your Kubernetes cluster to send logs without using the tools developed by SolarWinds.
rKubelog releases are referenced explicitly; ‘latest’ tags are not used. To update the image to the latest release, use the release’s current version:
<github_version> is the latest version listed in Releases. For example, when
r16 was the most recent release,
quay.io/solarwinds/rkubelog:r16 would have been used.
SolarWinds recommends that you subscribe to notifications of new releases in the rKubelog repo by clicking Watch and selecting Releases only from the drop-down.
By default, rKubelog runs in the
kube-system namespace and will observe all logs from all pods in all namespaces except from itself or from any other service in
<log destination host>:<log destination port>that displays at the top of the relevant log destination card on the Log Destinations page.
kube-systemnamespace with the following fields:
kubectl apply -k . --dry-run -o yaml
kubectl apply -k.
If you deploy rKubelog on nodeless clusters, such as EKS on Fargate, you may not see logs in Papertrail immediately. For EKS on Fargate, it may take up to two minutes for a pod to be fully deployed, as AWS needs to provision Fargate nodes. You can check the progress using:
kubectl get pods -o wide -n kube-system | grep rkubelog
If logs suddenly stop flowing, restart the rKubelog deployment:
kubectl scale deployment rkubelog --replicas=0 -n kube-system
kubectl scale deployment rkubelog --replicas=1 -n kube-system
If you are still having trouble viewing your logs or are unsure how to proceed, we’re happy to help. Contact us.