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.
로깅 메트릭 수집
fluent-bit 메트릭 연결을 통해 로그 기반 메트릭 수집 대시보드를 추가했습니다.
Tasks
Discussion
이제 로깅 커스텀을 할 차례인데 아마 기존 로그보다는 API-Server, Inference Server 로그만 수집하려고 합니다. 이유는 다음과 같습니다.
로깅 커스텀 태스크 과정을 통해서 API-Server, Inference Server에 대해서 메트릭을 보여준다면 Istio를 통한 인퍼런스 서버 평균 응답시간, TPS, Error Rate를 안해도 괜찮을까요?
다른 의견이 있다면 말씀해주세요~
Jira