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 #11492] Log/return query parameters in response metadata #33351

New Issue
Open
opened 2026-04-22 15:55:48 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-22 15:55:48 -05:00
Owner
Copy Link

Originally created by @maczg on GitHub (Jul 22, 2025).
Original GitHub issue: https://github.com/ollama/ollama/issues/11492

Currently, when making requests to Ollama with specific parameters (such as temperature, top_p, and top_k), there's no way to confirm which parameters were used by the model or to log them for debugging/auditing purposes.

It would be helpful to have one or both of the following:

  1. Response metadata: Include the effective parameters used in the response
  2. Server-side logging: Option to log the parameters of incoming requests (perhaps with a debug flag)

This would be particularly useful for:

  • Debugging parameter effects
  • Compliance/auditing requirements
  • Understanding default parameter behavior

I've reviewed the current API documentation and tested responses, but please let me know if this functionality already exists and I missed it.

Originally created by @maczg on GitHub (Jul 22, 2025). Original GitHub issue: https://github.com/ollama/ollama/issues/11492 Currently, when making requests to Ollama with specific parameters (such as temperature, top_p, and top_k), there's no way to confirm which parameters were used by the model or to log them for debugging/auditing purposes. It would be helpful to have one or both of the following: 1. **Response metadata**: Include the effective parameters used in the response 2. **Server-side logging**: Option to log the parameters of incoming requests (perhaps with a debug flag) This would be particularly useful for: - Debugging parameter effects - Compliance/auditing requirements - Understanding default parameter behavior I've reviewed the current API documentation and tested responses, but please let me know if this functionality already exists and I missed it.
GiteaMirror added the feature request label 2026-04-22 15:55:48 -05:00
GiteaMirror commented 2026-04-22 15:55:49 -05:00
Author
Owner
Copy Link

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

#10975

<!-- gh-comment-id:3102245905 --> @rick-github commented on GitHub (Jul 22, 2025): #10975
GiteaMirror commented 2026-04-22 15:55:49 -05:00
Author
Owner
Copy Link

@maczg commented on GitHub (Jul 22, 2025):

Thanks for the response!

The external tools suggestion makes sense as a workaround, but I'm wondering if there are specific reasons why exposing this information internally (either in response metadata or debug logs) wouldn't align with Ollama's goals?

<!-- gh-comment-id:3104000688 --> @maczg commented on GitHub (Jul 22, 2025): Thanks for the response! The external tools suggestion makes sense as a workaround, but I'm wondering if there are specific reasons why exposing this information internally (either in response metadata or debug logs) wouldn't align with Ollama's goals?
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#33351
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?