-
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
Librato
Introduction
Papertrail can create and update a Librato graph displaying the number of log messages matching a search alert.
Setup
Follow the steps in Alerts.
Settings
From Librato Account Settings, obtain this identifier:
- API Token
You will also need:
- The email address of the Librato account which the API token is associated with.
Then for the search alert you are creating, choose:
- Metric name, such as
Exploit attemptsorsystems.http.500.
Metric Attributes
Once the metric has appeared in Librato, select it, and then set the attributes as shown in the image below.
You may wish to modify:
Messages– Y-axis labelmsgs– Tooltip label- 60 – The Papertrail alert interval in seconds (60 for an alert that fires every minute)
