As from implementation view point it's absolutely clear that simple textarea on scheduled task editing page won't be able to do a log rotation and such stuff. This way we need a separate database table for that.
After thinking more about it it could be a great feature to allow logging data from any event, that requires it, not just an event triggered by scheduled task. For example if we have a custom code, that sends tweet about created link and it fails it then no way to show error (since it happens on editing popup close) and it writes error to a log, where everybody can see it.
Table could have "EventLogs" name and consists of following fields:
- LogId
- EventName (e.g. "ls:OnSubmitListing")
- LogDate (timestamp)
- LogMessage (text)
At any time we can easily pinpoint actual scheduled task (if any was involved) by matching EventName to one, that is specified in scheduled task definition.
Doesn't this look too familiar with "Remote Logging" discussion (
https://groups.google.com/d/topic/in-portal-dev/-YLc3RLkEtc/discussion)? Basically all logs about in-portal actions goes to that section where you can easily (far more easier, then scan large text files) process and rotate them all. Then all (or several) logs are pushed into the cloud (e.g. to
in-portal.com website) where support team can help customers to analyze them right away.