Would be great if it was possible to:
1. Enter a value in hours and once a history record is at least that old it would be automatically deleted? This would stop history getting too big and automatically remove old unneeded entries.
2. A similar option for Last Warnings as at present these can't be disabled.
3. An option to disable Last Warnings.
Cheers.
More Log Management Options?
Re: More Log Management Options?
Just wondering what everyone thinks of this? Might there be a chance of it making the future version soon? TIA.
Re: More Log Management Options?
Would be great to know if this could be considered? Thanks.
Re: More Log Management Options?
1. In the next release, history will be paged. Making this feature less relevant.
2. They're called "Warnings" for a reason! You should check them.
3. See 2
2. They're called "Warnings" for a reason! You should check them.
3. See 2
Re: More Log Management Options?
Thanks for reply.
I still can't see why a feature that would automatically delete old history records would not be useful.
I have read the warnings and they are just warnings and of no particular use to be kept for any length of time.
A feature is provided to control the general logging level/size of SABnzbd I just don't see why the other logging features (e.g. History and Warnings) aren't given the same treatment.
Seemed to be a good idea to me but what do I know
I still can't see why a feature that would automatically delete old history records would not be useful.
I have read the warnings and they are just warnings and of no particular use to be kept for any length of time.
A feature is provided to control the general logging level/size of SABnzbd I just don't see why the other logging features (e.g. History and Warnings) aren't given the same treatment.
Seemed to be a good idea to me but what do I know
Re: More Log Management Options?
The number of warnings will be reduced in later releases.
E.g. "missing articles" is something that should be summarized in the history.
Bad NZB's, servers complaining about missing authentication are things that must be reported.
Each feature costs time and there needs to be some kind of motivation for the
developers to implement it.
We already have so many crazy options, this would add another one, needing implementation
and explanation.
E.g. "missing articles" is something that should be summarized in the history.
Bad NZB's, servers complaining about missing authentication are things that must be reported.
Each feature costs time and there needs to be some kind of motivation for the
developers to implement it.
We already have so many crazy options, this would add another one, needing implementation
and explanation.
Re: More Log Management Options?
Thanks for taking time to reply. I see your point of view.
For me I do not want months worth of history/warnings hanging around for no useful reason. I like things focused to what I am doing.
I only need 24/36 hours so a feature that automatically removed them would be useful to me.
I can't even automate with wget Clear History/Clear Warnings as this would remove all entries even the newest.
Options called "Amount Of History To Keep (hours)" and "Amount Of Warnings To Keep (hours)" would not require any/much explanation and they can be made to start with sensible values or 0 to mean all or something.
What I like about SABnzbd is its configurability/power user options but if a developer does not like a suggestion I get that it will not be considered for implementation.
For me I do not want months worth of history/warnings hanging around for no useful reason. I like things focused to what I am doing.
I only need 24/36 hours so a feature that automatically removed them would be useful to me.
I can't even automate with wget Clear History/Clear Warnings as this would remove all entries even the newest.
Options called "Amount Of History To Keep (hours)" and "Amount Of Warnings To Keep (hours)" would not require any/much explanation and they can be made to start with sensible values or 0 to mean all or something.
What I like about SABnzbd is its configurability/power user options but if a developer does not like a suggestion I get that it will not be considered for implementation.