-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[service/telemetry] Add Configurable Log Rotation Support Using Lumberjack #13084
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.
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
base: main
Are you sure you want to change the base?
Changes from 18 commits
261777d
bfbb3ae
cb34be2
f3e26bd
e983202
bc93b76
b37b7cf
4bffa02
5687a28
ee9b2c2
dc8d06d
4b4f637
1452e83
dc3610f
c2aad65
d34b6b2
293d985
14f700f
dbc3236
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
# Use this changelog template to create an entry for release notes. | ||
|
||
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' | ||
change_type: enhancement | ||
|
||
# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver) | ||
component: service/telemetry | ||
|
||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
note: Added support for log rotation using lumberjack in the opentelemetry collector telemetry logger. | ||
|
||
# One or more tracking issues or pull requests related to the change | ||
issues: [10768] | ||
|
||
# (Optional) One or more lines of additional information to render under the primary note. | ||
# These lines will be padded with 2 spaces and then inserted directly into the document. | ||
# Use pipe (|) for multiline entries. | ||
subtext: | | ||
The Collector's internal telemetry logger now supports optional log file rotation using the lumberjack library. | ||
Configure `rotation` settings (max size, age, backups, compression) to manage log growth and retention directly, without needing external tools like logrotate. | ||
Applies rotation only if a valid file-based `output_paths` entry is provided. | ||
If `rotation.enabled` is false or the block is omitted, log behavior remains unchanged. | ||
Only affects file-based logging; no impact on default console targets like stdout, stderr logging or console environments. | ||
|
||
# Optional: The change log or logs in which this entry should be included. | ||
# e.g. '[user]' or '[user, api]' | ||
# Include 'user' if the change is relevant to end users. | ||
# Include 'api' if there is a change to a library API. | ||
# Default: '[user]' | ||
change_logs: [user] |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since I'm not familiar with the migration strategy here, I will look to an expert. Is it appropriate to be introducing new structs in the v0.3.0.go file (I would've expected that to be auto-generated / I'm no expert.).