Better logging on scheduled actions such as: email-in throttling, email-out in the last hour, GSA

I need to think about what we're really trying to accomplish and what a good UI would be. In the meantime, do you have any input as far as how what you're imagining differs from the output of mailin.log, which is accessible via the admin UI?

I hadn't looked recently so I didn't know you were logging that stuff for mailin and mailout. I could probably think of a better UI, but the priority isn't really high enough to warrant it.

The gsasync.log though is empty. For that, it would be nice to see:

a) That it is running. Or failing.

b) In each batch, what things it acted on, perhaps with some detail about the action. Within limits of course, but enough to get a little clue that something might be wrong.

--Paul

On Aug 4, 2010, at 10:38 AM, Chris Rossi wrote:

> I need to think about what we're really trying to accomplish and what a
> good UI would be. In the meantime, do you have any input as far as how
> what you're imagining differs from the output of mailin.log, which is
> accessible via the admin UI?
>
> --
> Better logging on scheduled actions such as: email-in throttling, email-out in the last hour, GSA
> https://bugs.launchpad.net/bugs/597837
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in KARL3: Confirmed
>
> Bug description:
> Administrators can find emailin gotchas a bit mysterious. Sure would be nice if we had an ADMIN screen with an entry for mailin that shows the most recent actions taken, to include throttling.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/karl3/+bug/597837/+subscribe

Improved logging for gsa_sync.

fixed