Configuring future logging

The role M3BE-FndAdmin is required for configuring future logging for jobs for other users. Users with the role M3BE-FndUser can view their own jobs but require the role M3BE-LogEnabler to configure future logging.

You can automatically capture detailed information from M3 Business Engine jobs before they start running using Future Logging. This is particularly useful for troubleshooting issues that occur intermittently or for monitoring specific job activities.

You can set up future logging to automatically start logging on new jobs that are started. When a job matching your criteria starts, logging automatically activates without manual intervention. Any future log configuration is active for, at most, 12 hours before logging is automatically removed.

These are the ideal scenarios for future logging:

  • Capturing logs from jobs that run on a schedule when you're not available to manually start logging
  • Troubleshooting intermittent issues that are difficult to reproduce
  • Monitoring specific users' job activities
  • Collecting diagnostic information for jobs that fail unpredictably

Use this procedure to configure future logging:

  1. Click Administration Tools > Business Engine Jobs.
  2. To configure future logging, select Logging > Configure future logging.
  3. Right-click or mark a future log configuration and select Remove to remove it.
  4. Select Add to create, right-click or mark a future log configuration and select Edit to update an existing future log configuration.
  5. Configure the scheduling options:
    1. To set up scheduled logging, specify a start date and time and end date and time for when the logging should be active. All times are in UTC. The maximum duration between start and end time is 12 hours.
    2. If no scheduled logging times are specified, the configuration will run immediately and remain active for 12 hours from the current time.
  6. Set up job identification:
    1. Specify the owner of the job. This determines which user's jobs will be monitored.
      Note: This field is only editable if the user has the role M3BE-FndAdmin.
    2. Specify the name of the job. Use exact job names or patterns to target specific jobs.
    3. Specify how many jobs the log configuration should be activated for. Maximum is 20.
  7. Configure the log content:
    1. On the Log Content tab, under Log levels, select the levels to enable logging.
    2. On the Log Content tab, under Components, select the components to enable logging.
    3. On the Log Content tab, under Concepts, select Enable concepts to enable concept logging and use the field to select the concept names to enable.
  8. Set filtering options:

    1. On the Advanced tab, select Show source location [Program.method:line] on each log line to include the Business Engine program, method, and line number that each log entry originates from.

    2. On the Advanced tab, specify filter entries to log only the calls that match one of the entries. Filtering is optional. If you specify no entries, everything is logged. Click Add filter entry to add an entry, and click the delete icon on an entry to remove it. You can specify a maximum of 20 entries. For each entry, specify these fields:
      • Program: the Business Engine program to match, for example MMS100.
      • Method: the method to match, for example PBCHK.
      • Line: the line number within the method. This field requires a method to be specified. Leave it blank to match all lines.
      • Depth: the maximum call depth from the log statement. Leave it blank for no limit.
      Each entry must specify at least a program, a method, or a line number. A blank field matches any value. In the Program and Method fields, you can use an asterisk to match any sequence of characters and a question mark to match a single character. For example, MMS* matches all programs with names that start with MMS, and *CHK matches all methods with names that end with CHK. The values are case-sensitive.
      Note: A filter entry that is never matched still consumes one of the configured jobs. For example, if you filter on a method that is never run, the log configuration is still used for that job.
  9. Set storage options:
    1. On the Advanced tab, use Backlog size to select the number of log entries to keep in the backlog.
    2. Select Log to file to save all log entries to a file on the host where the job is running. The file contains all log entries, not only the backlog, and is prefixed by JOBLOG-. You can download this file on the Business Engine Logs page.
  10. Click Save to save the future log configuration or Close to discard changes.