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

ful_SC-21036_size_processor_to_identify_large_logs #660

Merged
merged 6 commits into from
Jan 13, 2025
Merged

ful_SC-21036_size_processor_to_identify_large_logs #660

merged 6 commits into from
Jan 13, 2025

Conversation

fulyauluturk
Copy link
Contributor

No description provided.

otisg
otisg approved these changes Jan 10, 2025
View reviewed changes
Copy link
Member

@otisg otisg left a comment

Choose a reason for hiding this comment

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

LGTM. That "Identify Large Logs to Cut Logging Costs" is a little long. Some shorter variations, starting with original for easy visual comparison:

Identify Large Logs to Cut Logging Costs
Trim Big Logs to Cut Logging Costs
Trim Big Logs to Cut Costs

@fulyauluturk fulyauluturk merged commit 081e152 into master Jan 13, 2025
@fulyauluturk fulyauluturk deleted the ful-cut-costs-size-processor branch January 13, 2025 06:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@otisg otisg otisg approved these changes

@cpipilas cpipilas Awaiting requested review from cpipilas

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@fulyauluturk @otisg