# Solarwinds Logs

> Search and analyze DealerVision production logs via SolarWinds Observability API. Use when investigating errors, debugging issues, checking system health, or when the user mentions logs, SolarWinds, production errors, or system monitoring. Requires the `logs` CLI tool to be installed.

- Skill: `majiayu000/solarwinds-logs-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/solarwinds-logs-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/solarwinds-logs-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/solarwinds-logs-2

---


# SolarWinds Log Search

Search DealerVision production logs through the SolarWinds Observability API using the `logs` CLI tool.

## First-Time Setup

This skill requires the `logs` CLI tool and proper environment configuration.

### 1. Check if Already Installed

```bash
# Test if the tool is available
logs --help 2>/dev/null || echo "Not installed - setup required"

# Check environment variable
echo $SOLARWINDS_API_TOKEN
```

### 2. Install the Tool (One-Time Setup)

If the tool is not installed, run:

```bash
# From the agent-skills toolkit directory
cd /root/agent-skills

# Quick install (handles prerequisites automatically)
./init.sh --install-tool solarwinds-logs
```

**What this does:**
- Checks for .NET SDK 10.0+ (shows installation guide if missing)
- Installs the `logs` CLI tool globally (persists across sessions)
- Verifies the installation works
- Checks for required environment variables

**Note:** Installation only happens once - the tool becomes globally available.

### 3. Configure Environment Variable

The tool requires a SolarWinds API token for authentication:

```bash
# Option 1: Set for current session
export SOLARWINDS_API_TOKEN="your-token-here"

# Option 2: Set permanently (recommended)
echo 'export SOLARWINDS_API_TOKEN="your-token-here"' >> ~/.bashrc
source ~/.bashrc
```

**To obtain a token:**
1. Log in to SolarWinds Observability
2. Navigate to Settings → API Tokens
3. Create a new token with 'Logs Read' permission

### 4. Verify Setup

```bash
# Confirm tool is installed
dotnet tool list --global | grep SolarWindsLogSearch

# Confirm environment is configured
logs "test" --limit 1
```

## Prerequisites

- **.NET SDK 10.0+** (required to install the tool)
- **SOLARWINDS_API_TOKEN** environment variable (required to use the tool)
- Default data center: `na-01`

## Alternative: Manual Installation

If you prefer to install manually without the init script:

```bash
# Requires .NET SDK 10.0+
dotnet tool install --global DealerVision.SolarWindsLogSearch --version 2.4.0 --add-source /root/agent-skills/tools/solarwinds-logs

# Verify
logs --help
```

## Quick Commands

```bash
# Search for errors
logs "error" --time-range 1h

# Find specific exceptions
logs "DbUpdateException" --severity ERROR --limit 10

# Filter by service
logs "timeout" --program webhook-api --time-range 4h

# Get full details for a specific log entry
logs --id 1901790063029837827 --with-data

# Export large result sets to file
logs "exception" --time-range 24h --output-file results.json
```

## Key Options

| Option | Description |
|--------|-------------|
| `--time-range` | `1h`, `4h`, `12h`, `24h`, `2d`, `7d`, `30d` |
| `--severity` | `INFO`, `WARN`, `ERROR`, `DEBUG` |
| `--program` | Filter by service name (e.g., `media-processing`) |
| `--hostname` | Filter by host |
| `--limit` | Max results (default 1000, max 50000) |
| `--with-data` | Include structured JSON payload |
| `--no-data` | Exclude payload (faster, smaller response) |
| `--output-file` | Save full results to file |

## Workflow Strategy

1. **Start broad** - Run initial search without many filters
2. **Narrow progressively** - Add severity, time-range, or program filters based on results
3. **Retrieve details** - Use `--id` with `--with-data` for full log entry inspection
4. **Export large datasets** - Use `--output-file` for comprehensive analysis

## Output Format

Returns JSON with:
- `success`: boolean status
- `query`: search parameters used
- `summary`: statistics including severity breakdown, truncation info
- `results`: array of log entries with timestamps, source, severity, message
- `pagination`: info for getting more results

## Advanced Usage

For detailed documentation on query syntax, MCP server modes, and advanced patterns, see [references/REFERENCE.md](references/REFERENCE.md).

For common investigation patterns and recipes, see [references/RECIPES.md](references/RECIPES.md).