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
I have a need for a large number of devices to occasionally be able to upload logs. I think log rotate has most of the features I need but the email delivery would not be ideal.
I would like a new feature that would allow a configuration parameter that can specify an AWS S3 bucket and an STS token to allow log rotate to post segments as they fill up to S3.
I also need a feature so when I change a configuration value to enable logging that any segments still retained on the device are forwarded to S3. This allows me to have some logs that normally would just get written over get uploaded once we recognize a problem with the device. We would leave things configured to continue uploading log segments until we have been able to diagnose the problem then we would change the config back.
I may be able to get corporate sponsorship to fund implementing these features but only if we can ensure they become they become part of the core product that eventually rolls into openWrt.
Extra Credit feature: LogRotate would be reading files out of a temp directory (ram disk) and would write the archived segments into a different device where I have persistence across reboots. We want the log segments written there to re-use the same files of X segments of Y length by leaving the original file in place and overwriting the contents rather than creating new files because every time a file is created or deleted causes wear on the media which we need to avoid. The goal is to allow retention of critical logs for after the fact debugging after reboots while absolutely minimizing the number of times we write to the same sector.
I have a need for a large number of devices to occasionally be able to upload logs. I think log rotate has most of the features I need but the email delivery would not be ideal.
I would like a new feature that would allow a configuration parameter that can specify an AWS S3 bucket and an STS token to allow log rotate to post segments as they fill up to S3.
I also need a feature so when I change a configuration value to enable logging that any segments still retained on the device are forwarded to S3. This allows me to have some logs that normally would just get written over get uploaded once we recognize a problem with the device. We would leave things configured to continue uploading log segments until we have been able to diagnose the problem then we would change the config back.
I may be able to get corporate sponsorship to fund implementing these features but only if we can ensure they become they become part of the core product that eventually rolls into openWrt.
Extra Credit feature: LogRotate would be reading files out of a temp directory (ram disk) and would write the archived segments into a different device where I have persistence across reboots. We want the log segments written there to re-use the same files of X segments of Y length by leaving the original file in place and overwriting the contents rather than creating new files because every time a file is created or deleted causes wear on the media which we need to avoid. The goal is to allow retention of critical logs for after the fact debugging after reboots while absolutely minimizing the number of times we write to the same sector.
RE: Saving things into S3 using STS tokens
The text was updated successfully, but these errors were encountered: