.env.example

# Copy this file to .env and fill in your values:
#   cp .env.example .env
#
# The .env file is read from the current directory first, then from the
# directory containing lz-ai-query.py. Real environment variables and the
# --host / --token flags override it.

# Base URL of your LogZilla server (http:// or https://).
#
# Do NOT append /api -- this tool adds it itself. A pasted /api suffix is
# stripped rather than producing /api/api/..., but leaving it off is clearer.
#
# A base path IS supported, for a LogZilla behind a reverse proxy on a
# subpath (e.g. https://example.com/logzilla). Both the REST calls and the
# chat WebSocket are built from it, so set it here if that is your setup.
LZ_HOST=http://logzilla.example.com

# LogZilla API auth token.
#
# Tokens are created on the LogZilla server with the CLI, as root or via sudo
# -- there is no way to create one from the web UI:
#
#   sudo logzilla authtoken create
#   Creating USER token
#   user-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
#
# The token is the last line of the output. To create one for a specific
# LogZilla user, add -U <username>. List existing tokens with
# `logzilla authtoken list`, and revoke one with `logzilla authtoken revoke`.
#
# Use a full USER token. An ingest-only token (created with --ingest-only, and
# prefixed "ingest-") only works for sending events to /incoming and is
# rejected by the API this tool uses.
LZ_API_TOKEN=user-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

# LogZilla's own documentation uses LOGZILLA_HOST / LOGZILLA_API_KEY in its
# examples. This tool accepts those names too, so if you already export them
# for `logzilla query`, you can leave the two settings above unset.