Skip to content

docs: update access logging guide to use planoai logs command#924

Open
octo-patch wants to merge 1 commit intokatanemo:mainfrom
octo-patch:fix/docs-access-logging-command
Open

docs: update access logging guide to use planoai logs command#924
octo-patch wants to merge 1 commit intokatanemo:mainfrom
octo-patch:fix/docs-access-logging-command

Conversation

@octo-patch
Copy link
Copy Markdown

Relates to #648

Problem

The access logging guide showed tail -F ~/plano_logs/access_*.log to view access logs. This command only works when using the dev Docker Compose setup (config/docker-compose.dev.yaml) which mounts ~/plano_logs:/var/log/. It does not work with the standard planoai up workflow, where logs live inside the container (native mode: ~/.plano/run/logs/, Docker mode: /var/log/ inside the container).

Solution

Replace the manual tail command with planoai logs --follow, which works correctly in both modes:

  • Native mode (default): reads from ~/.plano/run/logs/access_*.log
  • Docker mode: uses docker exec to tail logs inside the container

Also add a note showing planoai logs --follow --docker for users running in Docker mode.

Testing

Verified against the CLI implementation in cli/planoai/utils.py and cli/planoai/native_runner.py.

Replaces the manual tail -F ~/plano_logs/access_*.log command with
planoai logs --follow, which works correctly in both native and Docker
modes. The local ~/plano_logs volume mount is only present in the dev
compose setup, not in the standard planoai up workflow.

Relates to katanemo#648
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant