DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to search mixed logs with an Elasticsearch-compatible API with Xerj

Index mixed log and data files into typed indices and query them with any Elasticsearch client.

Authorization notice. Xerj is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forAn operator or on-call engineer who needs to analyse incident logs in several formats without building a pipeline.

The problemMixed log formats need schema work and a pipeline before they can be searched, which slows incident response.

The outcomeLogs become queryable indices, and existing Elasticsearch clients and dashboards work against the same endpoint.

What you need first

  • A Linux, macOS or Windows machine on x86-64 or arm64
  • A local folder of code, docs, logs or PDFs to index
  • Claude Code or Cursor if you want the MCP and skill setup from xerj init
  • A terminal with curl and a shell

Steps

  1. curl -fsSL https://xerj.org/get | sh
  2. xerj --insecure --data-dir ~/xerj-data &
  3. xerj autoindex ~/logs (inferred, check the README)
  4. Query http://localhost:9200 with any Elasticsearch client, for example a standard _search request. (inferred, check the README)
  5. Check the indices created with the phase output and confirm record counts.

Prompt for your agent

Index <log directory> with xerj autoindex and answer <incident question> by querying the Elasticsearch-compatible API on http://localhost:9200. Expected output: the matching records and the index names used. Verify the record count against the indexing summary.

Caveat. The README says the API is Elasticsearch-compatible, but it does not list which specific endpoints or aggregations are supported, so test your queries first.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page