Our Papertrail integration allows Agents to search and analyze log data from your Papertrail account. (DEPRECATED: SolarWinds has migrated all Papertrail accounts into SolarWinds Observability)

​
Prerequisites

1

Open your Papertrail profile

Log in to your Papertrail account, and then go to Settings” > “Profile”.
2

Copy your API Token

Papertrail API Token

​
Configuration

Configure the Papertrail plugin by running uv run unpage configure or by editing the ~/.unpage/profiles/<profile_name>/config.yaml file: 
plugins:
  # ...
  papertrail:
    enabled: true
    settings:
      token: <your papertrail api token> # required
Alternatively, you can set the API token as an environment variable: 
export PAPERTRAIL_API_TOKEN="your-papertrail-api-token"

​
Tools

The Papertrail plugin provides the following tools to Agents and MCP Clients:

search_logs

Search Papertrail for logs within a given time range.Arguments
​
query
string
required
The search query. Use Papertrail’s search syntax to filter logs by hostname, program, message content, or other criteria. For example: “error”, “hostname:web01”, or “program:nginx AND status:500”.
​
min_time
datetime
required
The starting time for the search range (ISO 8601 timestamp). Logs generated at or after this time will be included in the results.
​
max_time
datetime
required
The ending time for the search range (ISO 8601 timestamp). Logs generated at or before this time will be included in the results.
​
timeout_seconds
integer
default:"10"
The maximum number of seconds to wait for the search to complete. Defaults to 10 seconds. Increase this value for more comprehensive results in large log volumes, or decrease it for faster response times.
Returns PapertrailSearchResult: An object containing:
  • results: Log events with details including timestamp, hostname, program, message, and metadata.
  • truncated: Boolean indicating if results were truncated due to response size limits.
  • timed_out: Boolean indicating if the search timed out based on the specified timeout.
Note: Results are automatically truncated if they exceed response size limits to ensure optimal performance.