Repository navigation
[NO-ISSUE] feat: LLM Obs dev/prod env 분리 및 스팬 태그 보강 - #134
Merged
Merged
Conversation
Contributor
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
요약 (Summary)
env:dev로 섞이던 문제를 고쳤습니다. Procfile의-Ddd.env=dev하드코딩을-Ddd.env=${DD_ENV:-dev}로 바꿔 EB 환경변수로 env를 정합니다.OpenAiChatClientImpl의 응답 파싱을 LLM 스팬 안으로 옮겨 JSON 파싱 실패도 error 스팬으로 남깁니다. 입출력, 토큰,finish_reason은 파싱 전에 기록해 잘린 응답이 원인일 때도 스팬에서 보입니다.use_case,prompt_hash(system 프롬프트 SHA-256 앞 8자),finish_reason,retries,graphql.operation,usr.id태그를 추가했습니다. GraphQL 경로도 REST처럼 MDC에usr.id를 넣습니다(UserIdArgumentGraphqlResolver).runCatching안이라 사용자 응답, 예외,ai_call로그는 그대로입니다. GraphQL 액세스 로그에usr.id가 새로 찍힙니다.PR 유형