[Feature Request]: log output path or log config path as environment variable or CLI option

[rudolfolah]

Describe the problem

Currently, the log output path goes to chroma.log located near the chromadb_path.

Overriding it, based on the CLI code, means copying/pasting the log_config.yml and rewriting the configuration to point to a different logging path.

It would be great to be able to specify the exact path where the log file should be stored or to point to a different configuration file path.

Describe the proposed solution

Support CHROMA_LOG_OUTPUT_PATH as an environment variable or --log-output as a command-line argument

CHROMA_LOG_OUTPUT_PATH=/var/chroma.log chroma
chroma --log-output=/var/chroma.log

Alternatives considered

Alternatively, allow the log_config.yml path to be specified so that the configuration for logging can be completely customized:

CHROMA_LOG_CONFIG_PATH=/home/my-user/configs/chroma_log.yml chroma
chroma --log-config=/var/chroma/log_config.yml

Importance

would make my life easier

Additional Information

No response

[tazarov]

Hey @rudolfolah, I am glad you find the CLI useful. The team is looking to expand its functionality and usefulness, and what you suggest regarding the logging path falls within that category of improvements.

This should be pretty easy to add to the codebase, but let us spend a few moments considering the overall logging situation as this may also present an opportunity for improvement.

[rudolfolah]

Thanks for the quick response, that sounds like a good plan.

And this may be useful to someone else, here's how I got it working with systemd:

chromadb.service systemd unit definition

[Unit]
Description=Chroma
After=network.target
StartLimitIntervalSec=0

[Service]
Type=exec
Restart=always
RestartSec=1
User=my-user
ExecStart=/home/my-user/.local/bin/chroma run --path '/home/my-user/chromadb' --port 8123
WorkingDirectory=/home/my-user

log_config.yml, goes into the WorkingDirectory from the chromadb.service configuration. Change the path in handlers.file.filename to output the log to another path.

version: 1
disable_existing_loggers: False
formatters:
  default:
    "()": uvicorn.logging.DefaultFormatter
    format: '%(levelprefix)s [%(asctime)s] %(message)s'
    use_colors: null
    datefmt: '%d-%m-%Y %H:%M:%S'
  access:
    "()": uvicorn.logging.AccessFormatter
    format: '%(levelprefix)s [%(asctime)s] %(client_addr)s - "%(request_line)s" %(status_code)s'
    datefmt: '%d-%m-%Y %H:%M:%S'
handlers:
  default:
    formatter: default
    class: logging.StreamHandler
    stream: ext://sys.stderr
  access:
    formatter: access
    class: logging.StreamHandler
    stream: ext://sys.stdout
  console:
    class: logging.StreamHandler
    stream: ext://sys.stdout
    formatter: default
  file:
    class : logging.handlers.RotatingFileHandler
    filename: /var/chroma.log
    formatter: default
loggers:
  root:
    level: WARN
    handlers: [console, file]
  chromadb:
    level: DEBUG
  uvicorn:
    level: INFO

[rudolfolah]

Just saw the merged PR that references this issue, awesome work!