에러 추적 개선을 위한 Sentry 환경 구축 #770
Merged
Conversation
This file contains 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
hgo641
pushed a commit
that referenced
this pull request
Apr 23, 2024
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.
에러 추적 환경 개선을 위한 Sentry 도입.
더 필요한거 있을 것 같다 싶으면 말해주십쇼
아래 사진들은 로컬 기준 예시. 프로덕션이랑 데브서버에서 돌아갑니다. 직접 들어가서 밑에 더 내려보면 로그들 더 자세히 나와있음.
슬랙에 띄워지는 메시지 일단 경로랑 어떤 에러인지만 띄웠고, 404같은거는 어지간해서는 들어갈일없고 env찾으려고 노력하는 요청들이 대부분이길래 warning으로 일단 띄워봤슴다
저번에 nginx 로그 뜯어볼때 어지러웠음...🙋🏻 More
close #763