Growl about logging changes?

[darmok]

How do I make Growl growl (and log the event) about changes in its logging?

Thx,
- Dan.

[The_Tick]

You cannot.

[darmok]

Perhaps it would be good to add this.

Right now growling just ends with no reason. Someone trying to put together a sequence of events will have no pointer sending him to the next log.

- Dan.

[bgannin]

Could you please elaborate on what scenario/usage you feel needs addressed?

[darmok]

Two main uses: System/app failure determination and Forensics.

As more apps use Growl, I think the importance of the growl's logs rises. Some apps are sending events to Growl that they previously didn't log at all. Some apps are sending events to Growl that they previously sent to console.

By cross referencing system, console, growl, and app logs, you can determine a really good post-mortom chain of events. Even if the user edited a log or three, the discrepency between the logs will point that out.

log-start, log-continued-to, and log-end type entries make rebuilding the chain much easier...

- Dan.

[The_Tick]

Hmm..

Brian, based on your change yesterday, we're basically disabling logging unless someone throws a defaults command right?

Darmok, since the logging will basically be hidden from now on, if you'd like to send in a patch to improve the logging however you want I do not see a problem with that.

[bgannin]

Correct.