github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-07 00:22:43 -05:00
Code Issues 14.5k Packages Projects Releases 120 Wiki Activity

[GH-ISSUE #5848] The logs do not contain the request content sent by the client. #3648

New Issue
Closed
opened 2026-04-12 14:25:54 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-12 14:25:54 -05:00
Owner
Copy Link

Originally created by @H9990HH969 on GitHub (Jul 22, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5848

To facilitate debugging of the program, I need to see the requests sent to the large model from the frontend. However, I've noticed that the request URLs and contents are not visible in the logs. Where can I find them?

I have deployed DBGPT using Docker.

Originally created by @H9990HH969 on GitHub (Jul 22, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5848 To facilitate debugging of the program, I need to see the requests sent to the large model from the frontend. However, I've noticed that the request URLs and contents are not visible in the logs. Where can I find them? I have deployed DBGPT using Docker.
GiteaMirror commented 2026-04-12 14:25:56 -05:00
Author
Owner
Copy Link

@rick-github commented on GitHub (Jul 22, 2024):

The request body is not logged. You can see the prompt sent to the inference engine by setting OLLAMA_DEBUG=1 in the server environment and searching for msg="generate request" in the logs. If you want the contents of the HTTP traffic you'll have to use external tools. I usually install tcpflow in my ollama container image and use that:

$ docker compose exec -it ollama apt install -y tcpflow
$ docker compose exec -it ollama tcpflow -c 'src port 11434 or dst port 11434'

Other tools like ngrep are also useful.

<!-- gh-comment-id:2242697973 --> @rick-github commented on GitHub (Jul 22, 2024): The request body is not logged. You can see the prompt sent to the inference engine by setting `OLLAMA_DEBUG=1` in the server environment and searching for `msg="generate request"` in the logs. If you want the contents of the HTTP traffic you'll have to use external tools. I usually install `tcpflow` in my ollama container image and use that: ``` $ docker compose exec -it ollama apt install -y tcpflow $ docker compose exec -it ollama tcpflow -c 'src port 11434 or dst port 11434' ``` Other tools like `ngrep` are also useful.
GiteaMirror commented 2026-04-12 14:25:56 -05:00
Author
Owner
Copy Link

@konstantin1722 commented on GitHub (Jul 23, 2024):

I used WireShark. I have ollama deployed on a regular pc, so I used such a filter to inspect how langchain composes some promts: ip.dst == 192.168.1.55 && tcp.dstport == 11434 && http. Accordingly, by slightly changing the filter you can intercept requests for the docker container.

<!-- gh-comment-id:2245262190 --> @konstantin1722 commented on GitHub (Jul 23, 2024): I used WireShark. I have ollama deployed on a regular pc, so I used such a filter to inspect how langchain composes some promts: `ip.dst == 192.168.1.55 && tcp.dstport == 11434 && http`. Accordingly, by slightly changing the filter you can intercept requests for the docker container.
GiteaMirror commented 2026-04-12 14:25:57 -05:00
Author
Owner
Copy Link

@dhiltgen commented on GitHub (Aug 1, 2024):

As mentioned above, by default, for privacy concerns, we intentionally do not log the contents of the requests on the server. If you enable debug logging, then much more logging is produced, including the prompts.

<!-- gh-comment-id:2264147003 --> @dhiltgen commented on GitHub (Aug 1, 2024): As mentioned above, by default, for privacy concerns, we intentionally do not log the contents of the requests on the server. If you enable debug logging, then much more logging is produced, including the prompts.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#3648
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?