Skip to content
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

Jump to bottom

[Other]: Standardizing Log Path: Migrating chat Service Startup Logs to _output/logs #398

Closed
kubbot opened this issue Jan 25, 2024 · 2 comments · Fixed by #397
Closed

[Other]: Standardizing Log Path: Migrating chat Service Startup Logs to _output/logs #398

kubbot opened this issue Jan 25, 2024 · 2 comments · Fixed by #397
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Milestone
v1.5

Comments

@kubbot
Copy link
Contributor

kubbot commented Jan 25, 2024

What would you like to share?

This change aligns the chat service's log path with that of our openim-server, unifying our project's log management approach. It also makes log storage and access more intuitive and efficient. This update is aimed at simplifying our log maintenance efforts and providing a more convenient path for future log analysis.

Additional information

Key changes include:

Modifying the log path configuration for the chat service from logs/ to _output/logs.
Ensuring all related documentation and configuration files reflect this path change.
Conducting necessary testing to ensure the effectiveness and stability of the new log path.
@kubbot kubbot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Jan 25, 2024
@kubbot kubbot added this to the v1.5 milestone Jan 25, 2024
@kubbot kubbot linked a pull request Jan 25, 2024 that will close this issue
Standardizing Log Path: Migrating chat Service Startup Logs to _output/logs #397
Merged
@cubxxw cubxxw mentioned this issue Jan 25, 2024
Merged
@kubbot
Copy link
Contributor Author

kubbot commented Mar 26, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot kubbot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 26, 2024
@kubbot
Copy link
Contributor Author

kubbot commented Apr 2, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
v1.5
Development

Successfully merging a pull request may close this issue.

Standardizing Log Path: Migrating chat Service Startup Logs to _output/logs openimsdk/chat
1 participant
@kubbot