Skip to main content
Our SolarWinds integration allows Agents to search and analyze log data from your SolarWinds Observability account.
  • search_logs: Search SolarWinds logs within a specified time range

​
Prerequisites

1

Open your SolarWinds profile

Log in to your SolarWnds account, with Admin permsionns, and then go to “Settings” > “Profile”.
2

Create an API Access Token

SolarWinds API Token

​
Configuration

Configure the SolarWinds plugin by running uv run unpage configure or by editing the ~/.unpage/profiles/<profile_name>/config.yaml file:
Alternatively, you can set these settings as environment variables:

​
Tools

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

search_logs

Search SolarWinds for logs within a given time range.Arguments
​
string
required
The search query. Use SolarWinds’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”.
​
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.
​
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.
​
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 SolarWindsSearchResult: An object containing:
  • results: Log events with details including timestamp and message.
  • 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. Choose your search term and time narrowly, and iterate with additional searches if necessary, rather than trying to return the entire log context.