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

[GH-ISSUE #3193] Enhance Chat History Logging for API Interactions on Windows Deployment #48480

New Issue
Open
opened 2026-04-28 08:37:20 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-28 08:37:20 -05:00
Owner
Copy Link

Originally created by @Mingzefei on GitHub (Mar 17, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/3193

What are you trying to do?

I've deployed Ollama on a Windows 10 server to make the API available within a local network. I've observed that the .ollama/history directory only records local command-line interactions, not capturing chats initiated over the network.

How should we solve this?

A unified logging system should be implemented that captures both prompts and responses for all interactions, regardless of whether they are initiated locally or over the network. This change would eliminate the need to enable debugging options for basic chat history logging.

What is the impact of not solving this?

The current limitation impacts the ability to audit and review interactions comprehensively, raising privacy concerns, especially when private information is shared via API chats. I'm currently relying on the partial logs available and manually enabling OLLAMA_DEBUG=1 to track prompts without responses, which is not ideal.

Anything else?

This issue stems from the discussions in this Discord link.

Originally created by @Mingzefei on GitHub (Mar 17, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/3193 ### What are you trying to do? I've deployed Ollama on a Windows 10 server to make the API available within a local network. I've observed that the `.ollama/history` directory only records local command-line interactions, not capturing chats initiated over the network. ### How should we solve this? A unified logging system should be implemented that captures both prompts and responses for all interactions, regardless of whether they are initiated locally or over the network. This change would eliminate the need to enable debugging options for basic chat history logging. ### What is the impact of not solving this? The current limitation impacts the ability to audit and review interactions comprehensively, raising privacy concerns, especially when private information is shared via API chats. I'm currently relying on the partial logs available and manually enabling `OLLAMA_DEBUG=1` to track prompts without responses, which is not ideal. ### Anything else? This issue stems from the discussions in this [Discord link](https://discordapp.com/channels/1128867683291627614/1218857328728608921).
GiteaMirror added the feature request label 2026-04-28 08:37:20 -05:00
GiteaMirror commented 2026-04-28 08:37:24 -05:00
Author
Owner
Copy Link

@syllith commented on GitHub (Jul 3, 2024):

Depending on what you're using to submit these API calls, you might be able to just log them yourself. I have my own chat client that tracks history, and while I choose not to log mine, you could create something that would allow it. If you're using nginx as a reverse proxy, you might be able to log the API calls that get sent through it.

<!-- gh-comment-id:2207358531 --> @syllith commented on GitHub (Jul 3, 2024): Depending on what you're using to submit these API calls, you might be able to just log them yourself. I have my own chat client that tracks history, and while I choose not to log mine, you could create something that would allow it. If you're using nginx as a reverse proxy, you might be able to log the API calls that get sent through it.
GiteaMirror commented 2026-04-28 08:37:30 -05:00
Author
Owner
Copy Link

@liangjs commented on GitHub (Oct 9, 2024):

Depending on what you're using to submit these API calls, you might be able to just log them yourself. I have my own chat client that tracks history, and while I choose not to log mine, you could create something that would allow it. If you're using nginx as a reverse proxy, you might be able to log the API calls that get sent through it.

When a third-party library uses ollama api, it is not easy to track into the library to find when and where the api is called.

<!-- gh-comment-id:2401132073 --> @liangjs commented on GitHub (Oct 9, 2024): > Depending on what you're using to submit these API calls, you might be able to just log them yourself. I have my own chat client that tracks history, and while I choose not to log mine, you could create something that would allow it. If you're using nginx as a reverse proxy, you might be able to log the API calls that get sent through it. When a third-party library uses ollama api, it is not easy to track into the library to find when and where the api is called.
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 feature request
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#48480
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?