-
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
IIS
IIS and Web apps running within it generate two types of log messages: access and error log files (from IIS itself), and app log messages (typically from a C# or ASP.NET app). Papertrail can accept logs from either or both.
To aggregate Windows event logs, see Configuring remote syslog from Windows.
Web app logs
For apps running in IIS, we recommend using either NLog or log4net as a logging library. For NLog, visit Papertrail’s NLog .NET logging setup page. For log4net, visit Papertrail’s log4net logging setup page.
IIS access and error logs
For IIS access logs and error logs, aggregate them as standard text log files. See Configuring remote syslog from Windows.
Support
Contact us if we can help with configuration or troubleshooting.