[Bug]: The request-response loogging doesn't include the principal

Open Beginner friendly
#3,003 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
google-cloud, jupyter-notebook
Domain
cloud, observability

Research direction

Open gemini/logging/intro_request_response_logging.ipynb and inspect how request-response logging is configured and demonstrated. Compare the notebook's logging table fields with the linked schema, then verify that the resulting logs include the principal alongside the project ID.

Written by the indexing model from the issue text.

Description

File Name

gemini/logging/intro_request_response_logging.ipynb

What happened?

Logs doesn't contain the principal that requested the endpoint hence there is no way to audit this. The logging table schema should not only the project id, but the principal that sent the request.

Relevant log output
Code of Conduct
  • I agree to follow this project's Code of Conduct
Dominant language
Jupyter Notebook
Stars
17.7k
Forks
4.5k
Avg merge
16h 46m
Merged PRs (30d)
41

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from GoogleCloudPlatform/generative-ai

All issues in GoogleCloudPlatform/generative-ai

Similar issues

More Cloud issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.