Control Panel

Opensolr Control Panel — find answers to your questions

The Complete Opensolr Platform Guide

Platform Guide
The Complete Opensolr Platform Guide
Everything you need to know about Opensolr — from creating your first Solr index to running a fully managed production search stack with AI-powered features, a built-in web crawler, and a complete REST API.

Managed Solr Hosting

Opensolr is a fully managed Apache Solr hosting platform. You get production-grade Solr clusters without managing servers, JVMs, or replication — we handle all of that.

Global Regions
US-East, US-West, EU-Central, EU-West, EU-North, Asia-Pacific — pick the region closest to your users.
Solr 5 through the latest Solr version available to date
Multiple Solr versions available. Upgrade at any time from the Control Panel.
Shared, Dedicated & Resilient
From free shared indexes to dedicated clusters with master + replicas for high-availability workloads.
HTTPS & Auth by Default
Every index comes with SSL encryption and HTTP Basic Auth. Add IP whitelisting for extra security.

Getting Started — Create Your First Index

SIGN UP
Create account
ADD NEW
Dashboard menu
SELECT REGION
Version + location
NAME + CREATE
Click Add Index
CONFIGURE
Upload schema, go!
From signup to live search in under five minutes

1. Create your account

Head to opensolr.com and click Sign Up. Enter your email, choose a password, and confirm via the activation email. Once logged in, you land on your Dashboard — the central hub for indexes, clusters, billing, team members, and API keys.

Opensolr Login

2. Open the Control Panel and click "Add New"

Click your username in the top-right corner, select Control Panel, then open My Indexes and click Add New.

Control Panel menu
Add New index

3. Choose your region and Solr version

Use the filter dropdowns to select a Region, Solr Version, and optionally a Country. Click the cluster card that matches your needs.

Select Region
Select Cluster

4. Name your index and create it

Give your index a meaningful name (e.g. my_website, product_search) or keep the auto-generated ID. Click Add Index — your index is provisioned in seconds with connection details, hostname, port, and credentials ready to use.

Name your index

5. Upload your configuration

Click your index name to enter its Index Control Panel, then go to Configuration. Edit config files live in the browser (schema.xml, solrconfig.xml, synonyms, stopwords) or upload a ready-made config zip for your CMS. Your index is now ready to receive data.

See Solr Configuration Files Dependency Flow for details on how config files work together.

Configuration Manager

The Opensolr Control Panel

A single web-based dashboard for managing every aspect of your Solr indexes — from live analytics and query monitoring to configuration, security, backups, and index tools.

Index Management
Create, delete, start, and stop indexes. Choose regions, Solr versions, and provision in seconds.
Schema & Config
Edit schema.xml, solrconfig.xml, synonyms, and stopwords directly in the browser — or upload a config zip.
Analytics & Monitoring
Query analytics with charts, bandwidth and disk usage, document counts, live query stream, and exportable PDF reports. Learn more
Security
HTTPS enforced by default. Manage HTTP Auth credentials, set up IP whitelisting, control per-index access. Learn more
Backup & Restore
One-click backups with instant restore, downloadable archives, and automated replication across regions. Learn more
Index Tools
Delete by query, reload, reset, commit, optimize, and restart Solr — all from the toolbar. Learn more
Team Management
Invite team members, assign roles, and manage shared access across all your indexes. Learn more
Query Interface
Run raw Solr queries directly from the panel. See real-time results, inspect response payloads, and debug without leaving the browser.
REST API Automation
Every action in the Control Panel is available via the REST API. Automate index creation, config uploads, backups, and more. See below
Opensolr Analytics Dashboard
Opensolr Index Overview

Connect Your Application

Drupal
Install Search API + Search API Opensolr. Add a server, enter your Opensolr hostname, port 443, path /solr/INDEX_NAME. Generate and upload the config set, create an index, and start indexing.
WordPress
Install WPSOLR or a similar Solr plugin. Enter your Opensolr host, port 443, path /solr/INDEX_NAME, and your auth credentials. Save and reindex.
Custom Application
Connect any app (PHP, Python, Node.js, Java, Ruby) directly to Solr's HTTP API with Basic Auth. Index via /update, query via /select. Supports JSON, XML, and CSV.
Moodle LMS
Connect Moodle's Global Search to Opensolr. Full integration tutorial covers setup, configuration, and troubleshooting.

Opensolr Web Crawler

Don't have an app backend or CMS? The Opensolr Web Crawler crawls any website and builds a fully indexed, searchable site — no code, no plugins, no infrastructure to manage.

Headless Chromium Rendering
Built-in Playwright-powered browser renders JavaScript-heavy pages — SPAs, React, Angular, Vue — no content left behind.
Multi-Format Extraction
Extracts content from HTML, PDF, DOCX, ODT, and XLSX files. Every page gets clean, structured text for indexing.
NLP Enrichment
Every crawled page is enriched with sentiment analysis (VADER), language detection, and price extraction from meta tags, JSON-LD, and microdata.
Embeddable Search UI
Add search to your site with two lines of HTML — or build a custom UI with the Solr API. Dark mode, scroll pagination, and more.
Search Analytics
Track what users search for, click-through rates, no-results queries, and content gaps — all built in.
Query Elevation
Pin pages to the top or exclude irrelevant results for specific queries. Full curation control from the dashboard.

App Server Management

Beyond Solr hosting, Opensolr manages your entire application stack — Drupal, Laravel, WordPress, or any framework running on your own servers or ours.

24/7 Monitoring & Auto-Healing
Watchdog service checks every server every 5 seconds. If a service goes down, it's automatically restarted before you notice.
Full Stack Support
Apache, Nginx, PHP-FPM, MySQL, Redis, Memcached, HAProxy, SSL certificates — we manage the entire stack so you can focus on your application.
Git CI/CD & DR Environments
Git-based deployments, staging environments, disaster recovery setups — enterprise-grade DevOps without the overhead.

Drupal Modules — Opensolr Turbo Indexer

Opensolr actively contributes to the Drupal ecosystem. Our flagship Drupal module is the Opensolr Turbo Indexer — a Drush-based parallel indexing engine that dramatically speeds up Solr indexing for large Drupal sites.

Parallel Batch Indexing
Run multiple indexing workers simultaneously. Index hundreds of thousands of documents in a fraction of the time it would take with standard Drupal cron.
Drush Integration
Simple Drush commands: drush ost --workers=3 --batch=100 for turbo parallel indexing, drush oss for stats, drush osstop to halt.
Background & Scheduled
Run indexing in the background with drush ost --background. Schedule via cron for fully automated, hands-free reindexing.

We also maintain the Search API Opensolr connector module, which simplifies connecting Drupal's Search API to any Opensolr-hosted index.


AI-Powered Search

Opensolr offers built-in AI search capabilities that go beyond traditional keyword matching.

Hybrid Search
Combines traditional keyword search with vector-based semantic search for results that understand meaning, not just words. Learn more
Vector Embeddings
Generate 1024-dimensional embeddings with BGE-m3 for any document. Single-doc and batch APIs available. Learn more
Search Tuning
Per-index relevancy controls — adjust field weights, boosting, and ranking strategies to fine-tune search quality. Learn more

REST API — Automate Everything

Every operation in the Opensolr Control Panel is available through the REST API. Automate index provisioning, config management, security, backups, crawling, and monitoring programmatically.

Quick API Examples

Once your index is live, interact with it directly via HTTP. Replace USER:PASS with your index credentials and CLUSTER.opensolr.com with your cluster hostname.

Search:

curl -u USER:PASS "https://CLUSTER.opensolr.com/solr/INDEX_NAME/select?q=laptop&rows=10&wt=json"

Index a document:

curl -u USER:PASS "https://CLUSTER.opensolr.com/solr/INDEX_NAME/update?commit=true" \
  -H "Content-Type: application/json" \
  -d '[{"id":"1","title":"My First Document","content":"Hello Solr!"}]'

PHP:

$url = 'https://CLUSTER.opensolr.com/solr/INDEX_NAME/select?q=laptop&wt=json';
$context = stream_context_create(['http' => [
    'header' => 'Authorization: Basic ' . base64_encode('USER:PASS')
]]);
$response = file_get_contents($url, false, $context);
$data = json_decode($response, true);
print_r($data['response']['docs']);

JavaScript:

const response = await fetch(
  'https://CLUSTER.opensolr.com/solr/INDEX_NAME/select?q=laptop&wt=json',
  { headers: { 'Authorization': 'Basic ' + btoa('USER:PASS') } }
);
const data = await response.json();
console.log(data.response.docs);

For a complete reference of all search parameters, see Querying the Solr API: Search Parameters Explained.


Troubleshooting

Issue Likely Cause Fix
Can't connect to Solr Wrong hostname, port, or credentials Check your Index Control Panel for the correct URL. Use port 443 for HTTPS.
No search results Content not indexed or schema mismatch Reindex your content. Ensure schema fields match what your app sends.
Drupal: "Server could not be reached" Config set not uploaded or wrong Solr version Upload the config set from Search API Solr. Check Solr version matches.
WordPress plugin error Plugin version incompatibility Update WPSOLR. Verify connection details.
Slow queries Unoptimized index or expensive queries Run Optimize from Tools, check Query Debugging.

Explore More


Ready to get started?
Sign up for free and have your first Solr index running in minutes.
Read Full Answer

Real-Time Solr Monitoring & Analytics

Real-Time Solr Monitoring & Analytics

Monitor Your Search Performance Like Never Before

OpenSolr brings enterprise-grade monitoring directly into your dashboard. No setup, no configuration, no external tools - just powerful real-time insights into your Solr infrastructure the moment you need them.


📈 Live Query Volume Tracking

Solr Query Volume Chart

See your search traffic as it happens. Our real-time query volume chart updates every second, giving you instant visibility into traffic patterns, usage spikes, and query trends.

Perfect for:

  • Identifying traffic patterns and peak usage times
  • Capacity planning and scaling decisions
  • Detecting unusual activity or traffic spikes
  • Understanding user behavior in real-time

🔍 Complete Query Stream Analysis

Query Stream Table

Every query that hits your Solr index is captured and displayed in real-time. See exactly what your users are searching for, how long queries take, and which searches are performing well.

What You Get:

  • Timestamp Precision - Track when every query executed
  • Full Query Details - See paths, parameters, and search terms
  • Performance Metrics - Response times displayed to the millisecond
  • Result Counts - Understand how many hits each query returns
  • Status Monitoring - Catch errors and issues instantly

Smart Filtering lets you search through thousands of queries using regex patterns on paths and parameters. Find exactly what you're looking for in seconds.


🔬 Deep Query Inspection

Query Parameters Modal

Click any query to see the complete breakdown. Every parameter, every filter, every detail - presented clearly and ready to analyze or test.

See Everything:

  • Complete query string ready to copy and test
  • All parameters displayed in an easy-to-read table
  • Multi-value parameters (like filter queries) shown properly
  • Clean formatting - no URL encoding clutter

Perfect for debugging, optimization, and understanding exactly what your application is sending to Solr.


⚡ Smart Slow Query Detection

Slow Queries Table

Slow queries hurt user experience and waste resources. Our intelligent slow query monitor automatically identifies and tracks queries that need attention.

Customizable Thresholds: Set your own definition of "slow" - from 0.2 seconds to 1.0 seconds - and let OpenSolr automatically flag queries that exceed your threshold.

Why It Matters:

  • Identify optimization opportunities
  • Find queries that need better indexing
  • Track performance improvements over time
  • Proactively address issues before users complain

Queries are sorted by response time, putting your slowest queries front and center where they belong.


🖥️ Real-Time Server Health Monitoring

Server Stats Dashboard

Your Solr server's vital signs, updated live. Monitor CPU, memory, disk usage, and load averages - all in one beautiful dashboard.

System Metrics Include:

  • CPU Usage - Real-time processor utilization with trend graphs
  • Memory Consumption - RAM usage tracking over time
  • System Load - 1, 5, and 15-minute load averages
  • Disk Capacity - Visual indicators show available space at a glance

Everything updates automatically - no refreshing needed. Just watch your infrastructure perform.


🎯 Getting Started

Accessing your monitoring dashboard is simple:

  1. Log into your OpenSolr Control Panel
  2. Select any of your Solr indexes
  3. Find the monitoring options in the left sidebar:
    • "Solr Log" for real-time query monitoring
    • "Server Monitor" for system health metrics

That's it. Your monitoring is already running, already collecting data, already ready to use.


✨ Why OpenSolr Monitoring Stands Out

Built for the way you work:

  • Zero Setup - Start monitoring the moment you create an index
  • Real-Time Updates - See changes as they happen, not minutes later
  • Millisecond Precision - Accurate performance metrics you can trust
  • Intelligent Filtering - Find the queries that matter
  • Always Included - No extra fees, no add-ons, no hidden costs

Professional tools at your fingertips: Every OpenSolr account includes full monitoring capabilities. Whether you're running a small blog or a high-traffic e-commerce platform, you get the same powerful insights.


💡 Real-World Benefits

For Developers: Debug issues faster, optimize queries with confidence, and understand exactly how your search is performing in production.

For Operations: Monitor server health, plan capacity needs, and catch problems before they impact users.

For Business: Understand search usage patterns, improve user experience, and make data-driven decisions about your search infrastructure.


📊 Web Crawler & Site Search Analytics

If you're using the Opensolr Enterprise Site Search (Web Crawler), there's a separate layer of analytics specifically for crawl-based search — covering crawl stats, search query analytics, click-through rates, and more.

👉 Solr-Level vs Web Crawler Search Analytics — a detailed comparison of both analytics systems and when to use each.


🚀 The OpenSolr Advantage

Professional search infrastructure shouldn't require enterprise budgets or DevOps teams. OpenSolr delivers powerful, production-ready monitoring as part of every account.

This is what modern search infrastructure looks like.


Monitoring is included with all OpenSolr plans. Log in now to start exploring your data.

Need help? Our team is here: support@opensolr.com | Documentation

Read Full Answer

Index Tools — Delete by Query & Utilities

Index Tools
Delete by Query & Index Utilities
The Tools panel in your Opensolr Control Panel gives you direct control over your index data and health — from targeted document deletion to full index maintenance and optimization.
WRITE QUERY
id:123 or *:*
PREVIEW
Verify matches
DELETE
Remove matched docs
COMMIT
Flush to disk
DONE
Changes live
Write a query, preview the results, delete, commit, done.

Delete by Query

Delete by Query lets you remove documents from your Opensolr index that match a specific Solr query. Instead of wiping your entire index and re-indexing from scratch, you can surgically target exactly the documents you want to remove — whether that is a single document by ID, an entire category, URLs matching a pattern, or records older than a certain date.

How to Access It

1
Open your Control Panel and click on your index name
Navigate to My Indexes, then click the name of the index you want to manage.
2
Click "Tools" in the sidebar menu
The Tools panel appears on the right side of the index Control Panel. It contains the Delete by Query form at the top, and the index utility buttons below.
3
Enter your delete query and click Delete
Type a valid Solr query into the text field, then click the red Delete button. Follow up with a Commit to make the changes visible in search results.

Query Syntax Examples

*:* — Deletes ALL documents in the index. Use with extreme caution. This is equivalent to a full wipe without resetting configuration.
id:12345 — Deletes a single, specific document by its unique ID. The safest and most precise way to remove one record.
uri:*site.com/path — Deletes all documents whose URI field contains "site.com/path". Useful for removing all pages under a specific path or domain.
category:news — Deletes all documents in the "news" category. Works with any indexed field — just replace "category" and "news" with your field name and value.
timestamp:[* TO 2024-01-01T00:00:00Z] — Deletes all documents with a timestamp before January 1, 2024. Range queries are perfect for cleaning up old or stale data.

After executing a delete query, always click Commit (or use the Commit utility button below) to flush the changes to disk and make the deletions visible in search results.


The Tools Panel

Here is what the Tools panel looks like in your index Control Panel. The Delete by Query form is at the top, followed by the utility buttons for index management operations.
Opensolr Index Tools Panel with Delete by Query and Utilities

Index Utilities

The utility buttons below the Delete by Query form give you full control over your index lifecycle — from reloading configuration to restarting the Solr process itself.

Reload
Reloads the Solr index configuration without restarting the Solr process. Use this after uploading new configuration files (schema.xml, solrconfig.xml, synonyms, stopwords, etc.). Changes take effect immediately and search remains available throughout — there is no downtime.
Reset
Wipes ALL data from your index completely. This is a destructive, irreversible operation — every document is permanently removed. Your configuration files (schema, solrconfig, etc.) remain intact. Use this when you need a completely fresh start, for example after changing your schema significantly and needing to re-index everything from scratch.
Commit
Forces Solr to flush all pending changes to disk and make them searchable. Solr normally auto-commits on a schedule, but after running a Delete by Query or bulk document update, use Commit to see the changes reflected in search results immediately rather than waiting for the next auto-commit cycle.
Optimize
Merges internal Solr index segments into fewer, larger segments. This improves query performance and reduces the disk footprint of your index. Optimization can be CPU-intensive on large indexes, so it is best to run it during low-traffic periods rather than during peak query load.
Schedule Optimize
Set up a recurring optimization schedule — daily, weekly, or at whatever interval suits your workload. This keeps your index segments merged and query performance optimal without requiring you to remember to run it manually. Set it once and your index stays fast automatically.
Restart Solr Service
Fully restarts the Solr process on your cluster node. This is a last-resort operation — use it if Solr becomes unresponsive, or after major configuration changes that require a full process restart rather than just a config reload. Your index will be briefly unavailable during the restart.

Pro Tips

Always commit after Delete by Query
Deletions are not visible in search results until you commit. After running a delete query, click the Commit button to flush the changes to disk immediately.
Test with SELECT before you DELETE
Before running a delete query, test it first by running the same query as a SELECT in the Solr Admin or via the API. This shows you exactly which documents will be affected, so you can verify before making any irreversible changes.
Reset is permanent — use it wisely
Reset wipes every document from your index. Only use it when you truly need to start from scratch — such as after a major schema redesign. For partial cleanup, Delete by Query is the better choice.
Schedule Optimize instead of running it manually
Rather than remembering to run Optimize periodically, use Schedule Optimize to automate it. Pick an off-peak time window and let Opensolr handle index maintenance in the background.

Explore More of the Control Panel
Learn how to create indexes, automate with the API, or reach out for help with your setup.
Read Full Answer

Error Audit — 7-Day Searchable Error History

Control Panel
Error Audit — 7-Day Searchable Error History
Every error your Solr index encounters is now automatically captured, parsed, and stored for 7 days. Search through stack traces, filter by severity and type, track error rates over time, and drill into any error with a single click — all from your Opensolr Control Panel.

How It Works

Every Opensolr cluster server continuously parses its Solr log files. Each ERROR, WARNING, and CRITICAL entry is automatically extracted, classified, enriched with a human-readable explanation, and indexed into a dedicated search index. This happens in the background — there is nothing to enable, configure, or maintain.

SOLR LOG
Raw log entries
PARSE
Extract & classify
INDEX
Searchable store
DASHBOARD
Search & analyze
Fully automatic — errors are captured and available within minutes

What gets captured for each error:

Timestamp
Exact time the error occurred, with date range filtering support.
Level & Severity
Critical (5/5), Error (4/5), or Warning (2/5) — with color-coded badges.
Error Type
Automatic classification: Solr, Memory, I/O, Timeout, Parsing, Security, Connection, or General.
Root Cause
The deepest exception in the Caused-by chain — the actual reason behind the error.
Plain-English Explanation
Every error includes a human-readable explanation of what went wrong and what to do about it.
Compacted Stack Trace
The important parts of the stack trace — first error line, exception chain, all Caused-by entries — without the noise.

The Error Audit Dashboard

Open any index in your Control Panel and click Error Audit in the left sidebar. The dashboard loads your error history instantly.

Summary Cards

At the top, four cards give you an at-a-glance breakdown: Critical, Errors, Warnings, and Total counts for the currently filtered view. These update dynamically as you change filters.

Error Rate Chart

A bar chart shows error frequency over the past 7 days, broken down by hour. Spot patterns immediately — recurring errors at specific times, sudden spikes after deployments, or a clean flat line when things are running smoothly.

Filters & Search

Full-Text Search
Search through stack traces and error messages. Find that one exception you saw yesterday — type any keyword and hit Enter.
Date Range
Pick a start and end date. Default is the last 24 hours, but you can go back up to 7 days to investigate past incidents.
Level & Type Filters
Click the level pills (Critical, Errors, Warnings) or use the Type dropdown to narrow down to specific error categories like Memory, I/O, or Parsing.

Errors Table

The main table shows every error in reverse chronological order. Each row displays the timestamp, level badge, error type, severity score, a truncated message, and which server it came from. Click any row to open the full detail view.


Error Detail View

Click any error in the table to open the detail modal. Everything you need to understand and fix the issue, in one place:

Plain-English Explanation
At the top of every detail view, a highlighted box explains the error in plain language. No Java stack trace decoding needed — you immediately know what went wrong.
Root Cause Extraction
The deepest Caused-by exception is extracted and shown separately. No more scrolling through 50 lines of stack trace to find what actually broke.

Below the explanation, you get the full technical breakdown:

  • Timestamp — exact time of the error
  • Server — which cluster server logged it
  • Level / Type / Severity — color-coded badges
  • Error Message — the raw message from the log
  • Root Cause — the deepest exception
  • First Log Line — the original line from solr.log
  • Stack Trace — compacted and syntax-highlighted, with Exception, Error, and Caused-by keywords highlighted in red for quick scanning

Error Types & Severity Levels

Every error is automatically classified into a type based on the exception class:

Type What It Means Common Cause
SOLRInternal Solr processing errorSchema mismatch, bad config, corrupt index
MEMORYOut of memory / heap exhaustionVery large result sets, complex queries, large documents
I/ODisk read/write failureDisk full, permissions, corrupt file
TIMEOUTQuery or operation took too longExpensive wildcard queries, unoptimized index
PARSINGMalformed query or documentInvalid query syntax, bad XML/JSON in updates
CONNECTIONNetwork connectivity issueTemporary network blip, DNS resolution failure
SECURITYAccess deniedAuthentication failure, IP restriction
GENERALUncategorized errorVarious — check the stack trace for specifics

Severity levels:

5/5
CRITICAL
4/5
ERROR
2/5
WARNING

Error Audit vs Tail Error Log

Opensolr now has two error views. They serve different purposes:

Tail Error Log
Real-time. Shows errors happening right now by tailing the live Solr log. Best for active debugging — watching errors appear as you test queries or push updates. Limited to the most recent entries in the current log file.
Error Audit
Historical. Searchable archive of every error from the past 7 days. Best for incident investigation, trend analysis, and auditing. Filter by date, search stack traces, see error rate patterns over time.

Use Tail when you need to see errors as they happen, right now. Use Audit when you need to find errors from the past, search for specific exceptions, or understand error trends.


Getting Started

  1. Log into your Opensolr Control Panel
  2. Select any of your Solr indexes
  3. Click Error Audit in the left sidebar
  4. Your error history loads automatically — use the filters, search, and chart to investigate

No setup, no configuration, no extra cost. Error Audit is included with every Opensolr account and works for every index across all plans.


Stop guessing. Start auditing.
Every Solr error, parsed, classified, and searchable — waiting for you in the Control Panel.
Read Full Answer