[
https://issues.apache.org/jira/browse/SLING-4407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14322819#comment-14322819
]
Stefan Egli commented on SLING-4407:
------------------------------------
bq. ...reassigned is missing. We could create OSGi events for that as well...
one argument against that would be that it then becomes part of the API and
would have to be supported going forward - even if we change the job
implementation entirely. But maybe that's not that much of a problem. Just
wondering who would be interested in receiving reassigned events and doing
anything based on it?
bq. we could log on each node whenever an action is taken
I was assuming it would work that way, yes. So more of a technical logging to
follow the job if something goes wrong - or to understand why a job was
'routed' to a particular node etc.
Re aggregation, I'd point to tools like splunk or similar..?
> introduce an audit-style logger to job handling
> -----------------------------------------------
>
> Key: SLING-4407
> URL: https://issues.apache.org/jira/browse/SLING-4407
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: Event 3.5.0
> Reporter: Stefan Egli
>
> To help with debugging issues around the job handling we could introduce an
> 'audit-style logger' which - when enabled - would log the most important
> actions available on each job, ie:
> * when the job is created
> * when it is assigned, reassigned
> * when it is finished/fails
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
