-
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
Elixir
Papertrail can accept logs from any Elixir app, with or without the
logger_papertrail_backend logging library.
Send log file with remote_syslog2
Configure your Elixir app to log to a file as usual, then transmit the log file to Papertrail using remote_syslog2. This does not require any modifications to the app.
Send events from Elixir app
Alternatively, the app can send a log message directly to Papertrail using the syslog protocol.
To do this, add logger_papertrail_backend to
the app and point it at Papertrail. See
Add Systems for the host and <port> log destination values.
Since logger_papertrail_backend is emitting UDP, which is inherently connection-less,
the write calls are non-blocking.