-
Administrator Guide
-
Collect Logs
-
Collect Logs: Apps & Services
- ESXi
- Routers network hardware
- Apple iOS and macOS
- Unix and BSD system logs
- C# and .NET (NLog)
- C# and .NET (log4net)
- Java logback
- Android
- Kubernetes cluster logging with rKubelog
- haproxy
- Advanced Unix logging tips
- Perl
- Windows
- Kubernetes
- Erlang
- Node.js
- Java log4j
- JavaScript
- Unicorn
- PHP
- Docker
- systemd
- Ruby on Rails
- MySQL
- Unix and BSD text log files (remote_syslog2)
- Redis
- Go
- Python
- Elixir
- IIS
- Embedded devices or proprietary systems
-
Collect Logs: Hosting Services
-
Collect Logs: Integrations
-
Manage Logs
- Groups
- Log flood detection
- Web Hooks
- Log colorization
- Linking to logs
- JSON search syntax
- Settings API
- Log destinations
- Alerts
- Command-line client
- Log filtering
- HTTP API
- Automatic S3 archive export
- Managing Senders
- Permanent log archives
- Mapping senders to groups
- Search syntax
- Click-to-search
- Log search API
- Event Viewer
-
Send Logs for Analytics
-
SolarWinds Users & Orgs
-
Support and Security
-
What's New
Cloud Foundry
Introduction
Cloud Foundry is a Platform-as-a-Service for deploying and scaling applications.
Setup
Create a Papertrail account (free)
If you don’t already have an account, sign up (free).
Register app with Papertrail
- Visit Add Systems: Less common setup methods and choose option B, I use Cloud Foundry.
- Fill in the form. Papertrail will provide a log destination to use with a Cloud Foundry log drain for your app. If you have multiple Cloud Foundry apps, register each app separately.
Set up Cloud Foundry drain
Add the Papertrail Log destination:
$ cf cups my-logs -l syslog-tls://logsN.papertrailapp.com:XXXXXreplacing logsN and XXXXX with the name and port number from the log destination created in the previous step.
Bind the service
Bind the newly created service drain to the app:
$ cf bind-service <appname> my-logsreplacing <appname> with the name of the application.
Apply the changes
Restart the application to start sending log data to Papertrail:
$ cf restart <appname>replacing <appname> with the name of the application.
Wait 30 seconds for logging to start. Once it starts, messages should appear in Papertrail’s Event viewer in realtime.
Notes
Unicorn
If you have added unicorn to your Cloud Foundry app stack, Papertrail’s Unicorn logging explanation may be useful.
The scripts are not supported under any SolarWinds support program or service. The scripts are provided AS IS without warranty of any kind. SolarWinds further disclaims all warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The risk arising out of the use or performance of the scripts and documentation stays with you. In no event shall SolarWinds or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the scripts or documentation.