Dan Klco created SLING-11797:
--------------------------------
Summary: Log Jobs Added with No Assigned Topology Capability at
Info
Key: SLING-11797
URL: https://issues.apache.org/jira/browse/SLING-11797
Project: Sling
Issue Type: Bug
Components: Event
Affects Versions: Event 4.3.6
Reporter: Dan Klco
Fix For: Event 4.3.8
When creating a job where the topology does not provide a capability for the
topic, the JobManagerImpl logs the following message at the DEBUG level:
{quote}Persisting job {} into queue {}{quote}
This makes it challenging to identify/diagnose issues with jobs not being
assigned as: * It requires enabling debug logging on the JobManagerImpl which
can be quite verbose, especially under load
* Since most production instances do not run with DEBUG, these situations will
not be available in logs
* The log message does not indicate that this job will not be immediately
assigned to be processed
Instead, the JobManagerImpl should log a message at least at INFO level which
indicates that the Job being persisted does not have an assigned target.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
