Long tasks run as jobs

Some panel actions take longer than one web request may stay open, such as rescanning your logs or deleting your indexes. Loghound runs them as jobs: a list of named steps you watch complete one by one, so a tab never dies halfway with no idea whether anything ran.

• Rescan log sources (Settings › Log sources): looks for access logs, then reads each file and saves the report.
• Check the Solr connection and check the Opensolr account (Settings › Solr connection).
• Check the index schema (Settings › Solr connection).
• Preview what retention would delete (Settings › How much data you keep). It only counts.
• Start over (Settings › Start the installation over). The only job that deletes anything: both Loghound indexes, then this installation’s data. Start over.

The browser installer uses the same mechanism for creating your indexes.

• One step per request. The page asks for the next step, the server runs exactly one and answers. No step comes near the request time limit, however long the whole job takes.
• No background process. Progress is kept in a small local database file, so a job survives a page reload.
• One job of a kind at a time. A double click, a reload or a second window all land on the same job.
• Real progress. The steps are known in advance, so the bar shows a true fraction.
• Cancel between steps. Cancel takes effect before the next step starts, never in the middle of one.
• Private to your sign-in. Another user cannot see, advance or cancel your job, and a finished job is cleared after an hour.