Loghound does not merely read and write its two indexes. It owns them — and that single fact is the whole reason there is no bring-your-own-Solr path.
Create an account · Sign in · What the plans hold. Setup asks for the account email and the API key, which is under Account in the control panel, and does the rest itself.
Across the life of an installation, Loghound does all of this to its two indexes:
- Creates them, with names it generates, in a region you pick from the list the platform returns.
- Uploads their configsets — schema first, then
solrconfig.xml, because reversed the core reloads against a config referring to field types the old schema does not define and the reload fails. - Reloads the cores and queries each one to prove it can reach and authenticate to them.
- Checks their shape against this release, field by field, whenever it joins a pair rather than creating one.
- Reports and trims them against your plan, which is what makes retention scale with the plan instead of being cut off by it.
On a Solr you administer yourself it has no route to create a core or install a configset, and no way to keep the schema right. The option existed once and was removed for exactly that reason: it promised something the product cannot deliver.
Loghound is self-hosted software. There is no Loghound company, no telemetry and no vendor with a copy of your traffic. But the claim “nothing leaves the box” was only ever true on the path that was removed, and this documentation will not repeat it.
| Destination | What is sent | Can it be turned off? |
|---|---|---|
| Your two Opensolr indexes | Everything Loghound stores — every hit and session document | No |
| The Opensolr platform API | Your account email and API key, and the index names being created or checked. No visitor data. During setup, and afterwards for the credential check and the plan figures | No |
| Geolocation, ASN, whois, reverse DNS | Visitor IP addresses, for enrichment | Yes, each individually |
So your log-derived data leaves your machine for infrastructure Opensolr runs. That is a processor relationship and you should treat it as one in your records. What you keep full control of is what is written: the IP mode decides whether an address is stored at all, and every enrichment lookup is a switch. Privacy is the page for that.
customAn installation made before the option was removed still has solr.mode => 'custom' in its configuration. It is refused, loudly and on purpose: the tail, score and retention commands all validate at startup and refuse to start, printing what changed, why, and what to do; the panel’s settings page says the same at the top of the Solr card.
To move, set solr.mode to 'opensolr' and run the wizard, which provisions the two indexes on your account:
sudo -u loghound php /opt/loghound/bin/loghound-setup
The new indexes start empty, and Loghound backfills only as far as your own log retention reaches. Your old cores are untouched; delete them when you no longer want them.