You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 26, 2023. It is now read-only.
* This Readme explains about managing logs for various s3 components.
#S3server:
s3server manages it's logging through script s3logfilerollover.sh. this is added in cron.hourly to run per hour.for customizing logging configuration "/etc/cron.hourly/s3logfilerollover.sh" should be changed. configure following parameters -
- S3_LOG_FILE_MAX_SIZE in "/opt/seagate/cortx/s3/s3config.yaml" and
- log_files_max_count in "/etc/cron.hourly/s3logfilerollover.sh"
as per your requirement.
#s3authserver:
s3authserver manages it's logging through log4j2.you have to enable loglevel option in authserver.properties to genrate auth
server logs.for customizing logging configuration "/opt/seagate/cortx/auth/resources/authserver-log4j2.xml" should be changed.
#haproxy:
haproxy manages it's logging through logrotate.for customizing logging configuration "/etc/logrotate.d/haproxy" should be changed.
#s3backgrounddelete:
s3backgrounddelete manages it's logging through rotating handler module.for customizing logging configuration "/opt/seagate/cortx/s3/s3backgrounddelete/config.yaml" should be changed.configure following parameters -