Skip to content

[Feat] Promtail, Loki 설정 #203

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hyomee2 wants to merge 5 commits into
base: develop
Choose a base branch
from
Open

[Feat] Promtail, Loki 설정 #203

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
ebae4e4
[Chore] #195 Prometheus 설정에 application 라벨 추가
hyomee2 Mar 24, 2026
4c87c94
[Feat] #195 Promtail 관련 설정 추가
hyomee2 Mar 24, 2026
036a407
Merge branch 'develop' of https://github.com/team-kareer/kareer-serve…
hyomee2 Mar 24, 2026
7ee710b
[Chore] #195 Promtail 이미지 태그 고정
hyomee2 Mar 26, 2026
0236973
[Chore] #195 볼륨 마운트 경로 맞도록 수정
hyomee2 Mar 26, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion deployment/docker-compose-monitoring.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
version: "3.8"
version: '3.8'

networks:
monitoring:
Expand Down
24 changes: 24 additions & 0 deletions deployment/docker-compose-promtail.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
version: '3.8'

services:
promtail:
image: grafana/promtail:3.6.0
container_name: promtail
restart: unless-stopped
env_file:
- .env
environment:
MONITORING_HOST: ${MONITORING_HOST}
volumes:
# 메인(애플리케이션) 서버 로그 폴더를 컨테이너 경로로 마운트
- ./logs/blue/info:/app/logs/blue/info
- ./logs/blue/warn:/app/logs/blue/warn
- ./logs/blue/error:/app/logs/blue/error

- ./logs/green/info:/app/logs/green/info
- ./logs/green/warn:/app/logs/green/warn
- ./logs/green/error:/app/logs/green/error

# Promtail 설정 파일
- ./promtail/promtail-config.yml:/etc/promtail/config.yml
command: -config.file=/etc/promtail/config.yml
Comment thread
hyomee2 marked this conversation as resolved.
10 changes: 10 additions & 0 deletions deployment/docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,13 +12,18 @@ services:
- REDIS_HOST=redis
- REDIS_PORT=6379
- REDIS_PASSWORD=
- LOG_BASE=/app/logs
env_file:
- .env
networks:
- kareer-net
depends_on:
- redis
restart: always
volumes:
- ./logs/blue/info:/app/logs/info
- ./logs/blue/warn:/app/logs/warn
- ./logs/blue/error:/app/logs/error

kareer-green:
image: ${ECR_REGISTRY}/kareer-server:${IMAGE_TAG}
Expand All @@ -31,13 +36,18 @@ services:
- REDIS_HOST=redis
- REDIS_PORT=6379
- REDIS_PASSWORD=
- LOG_BASE=/app/logs
env_file:
- .env
networks:
- kareer-net
depends_on:
- redis
restart: always
volumes:
- ./logs/green/info:/app/logs/info
- ./logs/green/warn:/app/logs/warn
- ./logs/green/error:/app/logs/error

redis:
image: redis:7.2-alpine
Expand Down
6 changes: 4 additions & 2 deletions deployment/prometheus/prometheus.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,8 @@ global:
scrape_configs:
- job_name: 'kareer_server'
metrics_path: '/actuator/prometheus'
scheme: https
static_configs:
- targets: ['api.ka-reer.com:443'] # HTTPS를 통해 접근
scheme: https
- targets: [ 'api.ka-reer.com:443' ] # HTTPS를 통해 접근
labels:
application: kareer_server
60 changes: 60 additions & 0 deletions deployment/promtail/promtail-config.yml
View file
Open in desktop
Copy link
Copy Markdown
Collaborator

@jeong1112 jeong1112 Mar 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

저희가 현재 Blue, Green 컨테이너로 나눠놓은 것은 버전 관리가 아니고 무중단 배포를 하기 위함인데 로그를 분리해서 저장하는 이유가 있나요?

Copy link
Copy Markdown
Collaborator Author

@hyomee2 hyomee2 Mar 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

장애 영향 범위를 최소화 하여 원인이 발생한 컨테이너에 대해서만 로그를 확인할 수 있어 더 유용하고, 롤백을 하게 될 경우에도 어떤 환경의 문제/로그인지 빠르고 정확하게 확인할 수 있다는 점에서 분리했습니당.

Original file line number Diff line number Diff line change
@@ -0,0 +1,60 @@
# Promtail이 로그를 어디까지 읽었는지 기록
positions:
filename: /tmp/positions.yaml

clients:
- url: http://${MONITORING_HOST}:3100/loki/api/v1/push # 모니터링 서버의 Loki 주소
scrape_configs:
- job_name: info_blue
static_configs:
- targets:
- localhost
labels:
job: info_logs
deployment: blue
__path__: /app/logs/blue/info/*.log

- job_name: info_green
static_configs:
- targets:
- localhost
labels:
job: info_logs
deployment: green
__path__: /app/logs/green/info/*.log

- job_name: warn_blue
static_configs:
- targets:
- localhost
labels:
job: warn_logs
deployment: blue
__path__: /app/logs/blue/warn/*.log

- job_name: warn_green
static_configs:
- targets:
- localhost
labels:
job: warn_logs
deployment: green
__path__: /app/logs/green/warn/*.log

- job_name: error_blue
static_configs:
- targets:
- localhost
labels:
job: error_logs
deployment: blue
__path__: /app/logs/blue/error/*.log

- job_name: error_green
static_configs:
- targets:
- localhost
labels:
job: error_logs
deployment: green
__path__: /app/logs/green/error/*.log
72 changes: 72 additions & 0 deletions src/main/resources/logback-spring.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,72 @@
<configuration>

<property name="LOG_BASE" value="${LOG_BASE}"/>
<property name="APP_NAME" value="kareer-server"/>

<!-- 콘솔 로그 -->
<appender name="CONSOLE" class="ch.qos.logback.core.ConsoleAppender">
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss} [%level] [%thread] %logger{36} - %msg%n</pattern>
</encoder>
</appender>

<!-- INFO 로그 -->
<appender name="INFO_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${LOG_BASE}/info/${APP_NAME}.info.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>${LOG_BASE}/info/${APP_NAME}.info.%d{yyyy-MM-dd}.log</fileNamePattern>
<maxHistory>7</maxHistory>
</rollingPolicy>
<filter class="ch.qos.logback.classic.filter.LevelFilter">
<level>INFO</level>
<onMatch>ACCEPT</onMatch>
<onMismatch>DENY</onMismatch>
</filter>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss} [%level] [%thread] %logger{36} - %msg%n</pattern>
</encoder>
</appender>

<!-- WARN 로그 -->
<appender name="WARN_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${LOG_BASE}/warn/${APP_NAME}.warn.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>${LOG_BASE}/warn/${APP_NAME}.warn.%d{yyyy-MM-dd}.log</fileNamePattern>
<maxHistory>7</maxHistory>
</rollingPolicy>
<filter class="ch.qos.logback.classic.filter.LevelFilter">
<level>WARN</level>
<onMatch>ACCEPT</onMatch>
<onMismatch>DENY</onMismatch>
</filter>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss} [%level] [%thread] %logger{36} - %msg%n</pattern>
</encoder>
</appender>

<!-- ERROR 로그 -->
<appender name="ERROR_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
<file>${LOG_BASE}/error/${APP_NAME}.error.log</file>
<rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
<fileNamePattern>${LOG_BASE}/error/${APP_NAME}.error.%d{yyyy-MM-dd}.log</fileNamePattern>
<maxHistory>7</maxHistory>
</rollingPolicy>
<filter class="ch.qos.logback.classic.filter.LevelFilter">
<level>ERROR</level>
<onMatch>ACCEPT</onMatch>
<onMismatch>DENY</onMismatch>
</filter>
<encoder>
<pattern>%d{yyyy-MM-dd HH:mm:ss} [%level] [%thread] %logger{36} - %msg%n</pattern>
</encoder>
</appender>

<!-- Root 로그 -->
<root level="INFO">
<appender-ref ref="CONSOLE"/>
<appender-ref ref="INFO_FILE"/>
<appender-ref ref="WARN_FILE"/>
<appender-ref ref="ERROR_FILE"/>
</root>

</configuration>
Loading