Problem

Currently, Rundeck mixes application-level error messages with job execution errors in the same log files (service.log and rundeck.log). This makes it difficult for administrators to distinguish between:

• Issues originating from Rundeck application itself (requiring admin investigation)
• Issues from job executions (requiring user/job owner investigation)

Use Case

Enterprise administrators managing multiple teams need to quickly identify the root cause origin of issues to:

• Route problems to the appropriate team (admins vs job owners)
• Prioritize incidents based on scope (application-wide vs single job)
• Separate operational concerns from user-triggered errors

Current Behavior

Both application errors and job execution errors appear interleaved in:

• service.log
• rundeck.log

Requested Enhancement

Separate logs into distinct categories:

1. Application logs: Rundeck core errors, startup issues, plugin failures, system-level problems
2. Job execution logs: Job failures, script errors, node execution issues, user-triggered problems

Suggested Implementation

Options:

• Separate log files (e.g., rundeck.application.log vs rundeck.jobs.log)
• Log level/marker differentiation in existing files
• Configurable log routing in log4j2.properties

Benefits

• Faster incident triage and root cause analysis
• Clearer separation of responsibilities (admins vs users)
• Better log management and retention policies per log type
• Improved CloudWatch/monitoring alerting accuracy