Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include more information about the caller #80

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

kerinin
Copy link
Collaborator

@kerinin kerinin commented Sep 25, 2024

Currently, when making calls to AstraDB, we include a User-Agent header identifying the API caller. This header is currently set to "langchain" by default at the moment. This change threads the caller_name parameter throughout the API and appends a suffix identifying which class created the API client:

  • langchain/cache
  • langchain/chat_message_history
  • langchain/document_loader
  • langchain/graph_vectorstore
  • langchain/semantic_cache
  • langchain/vectorstore

This metadata will be useful for debugging and tracking utilization of different library features.

NOTE: This change will change the value of User-Agent headers, for
example from langchain/0.3.6 to langchain/vectorstore/0.3.6

Currently, when making calls to AstraDB, we include a `User-Agent`
header identifying the API caller. This header is currently set to
"langchain" by default at the moment. This change threads the
`caller_name` parameter throughout the API and appends a suffix
identifying which class created the API client:

* langchain/cache
* langchain/chat_message_history
* langchain/document_loader
* langchain/graph_vectorstore
* langchain/semantic_cache
* langchain/vectorstore

This metadata will be useful for debugging and tracking utilization of
different library features.

NOTE: This change will change the value of User-Agent headers, for
example from `langchain/0.3.6` to `langchain/vectorstore/0.3.6`
@hemidactylus
Copy link
Collaborator

This should be discussed a bit more before merging, as it involves possible changes across several layers (e.g. usage analytics automation, etc). Let us first ensure everyone is aligned on how we want to achieve this.

@hemidactylus hemidactylus added the do_not_merge Do not merge yet, requires further discussion label Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do_not_merge Do not merge yet, requires further discussion
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants