-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Log compression for structured logging #16475
Copy link
Copy link
Open
Labels
C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-needs-designStatus: Needs someone to work further on the design for the feature or fix. NOT YET accepted.Status: Needs someone to work further on the design for the feature or fix. NOT YET accepted.Z-build-analysisNightly: build-analysisNightly: build-analysis
Description
Metadata
Metadata
Assignees
Labels
C-feature-requestCategory: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`S-needs-designStatus: Needs someone to work further on the design for the feature or fix. NOT YET accepted.Status: Needs someone to work further on the design for the feature or fix. NOT YET accepted.Z-build-analysisNightly: build-analysisNightly: build-analysis
Type
Fields
Give feedbackNo fields configured for issues without a type.
Problem
-Zbuild-analysishas become Cargo's structured logging system, though the current logging infrastructure is still not polished.https://github.com/rust-lang/cargo/blob/b53c96b634c1ad10174a414c42287a4a399eec77/src/cargo/util/logger.rs
We may need log compression.
Proposed Solution
It is not necessary to have a built-in solution in Cargo. If ever have, we might want to
build-analysistable, we can have some config file enabling log rotation.We should also look at external logging system, and see if there is a possible way for users to easily integrate Cargo with them, and make Cargo there so we don't need to invent the same thing again.
Notes
Part of #15844