microsoftgraph / microsoftgraph/msgraph-sdk-python

Excessive Informational Logs from Library During HTTP Requests

未关闭
#1,130 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

主要语言
Python
星标
630
派生
96
平均合并
15 小时 20 分钟
30 天内合并 PR
3

描述

I am using the library as shown below and I am flooded from logs coming from the library:

2025-02-11 17:17:37,072 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,119 - INFO - ClientSecretCredential.get_token succeeded
2025-02-11 17:17:37,199 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,249 - INFO - ClientSecretCredential.get_token succeeded
2025-02-11 17:17:37,330 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,391 - INFO - ClientSecretCredential.get_token succeeded
2025-02-11 17:17:37,470 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,516 - INFO - ClientSecretCredential.get_token succeeded
2025-02-11 17:17:37,591 - INFO - HTTP Request: GET https://graph.microsoft.com/v1.0//users/REDACTED "HTTP/2 200 OK"
2025-02-11 17:17:37,641 - INFO - ClientSecretCredential.get_token succeeded

How do I make it stop?

async def find_user(client: GraphServiceClient, user_id: str) -> None:

    query_params = UserItemRequestBuilder.UserItemRequestBuilderGetQueryParameters(
		expand = ["manager($levels=max;$select=id,displayName,mail,department,jobTitle)"],
		select = ["customSecurityAttributes","id","displayName","mail","department","jobTitle"],
    )

    request_configuration = RequestConfiguration(
        query_parameters = query_params,
    )

    return await client.users.by_user_id(user_id).get(request_configuration = request_configuration)

Originally posted by @Marcuccio in https://github.com/microsoftgraph/msgraph-sdk-python/discussions/1112

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

从提供的 find_user 入口点开始,使用 GraphServiceClient 和所示的请求配置重现重复的信息输出。跟踪发出 HTTP 和凭据消息的库组件;当请求在没有过多信息日志的情况下仍能正常工作,并且该行为由适当的回归检查覆盖时,即视为完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
python
领域
api, backend
Issue 类型
缺陷
难度
3/5
预计耗时
1-2 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
35/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。