Filewalker Log entries... missing?

i was looking for the file walker entries in my logs and was a bit surprised that i was unable to find it there, i did a grep for the terms file or walk and nothing relevant came up…

am i just getting the entry name wrong or can it really be that the filewalker start and finish doesn’t appear in the logs even while running on debug.

i know this is most likely an oversight, because even if the filewalker log entry isn’t relevant for Storjlabs development purposes, then it should still be there for whatever usage people might have of it…

the filewalker is a substantial task that can adversely affect some systems, so it should be logged like anything else relevant, because the whole purpose of a log is to be a map to correlate events to in time, thus one can look at other logs and correlate from say hdd behavior or failures and work back towards finding the cause of the overload lets say.

sure it might not be very useful, nor may it ever be used… but it should still be there… because we cannot predict what kind of issues people will be troubleshooting, which is why anything that can be logged without issue, should be… and since it would only be like 0.00001% or less of the logs, then it makes no sense not to log it.

but hey maybe i’m wrong maybe it just has a different name??

Good idea I think.

@SGC what did you have in mind exactly when you said

So I assume the idea would be to only log whenever the file walker starts, and whenever it’s done?

1 Like

yes, i was just referring to that logs are good, but it\s not always possible to log everything…
in this case ofc the log entries would be nothing…

basically i want to log everything that can be logged without causing performance or storage issues when it comes to logs, even by default… so i don\t understand how they could leave out the filewalker…

1 Like