Logging level for an Automation Script must be set in which two places?

Question

Options

• Aon the Console appender in Logging application
• Bon the autoscript logger in Logging application
• Con the Logging in Automation Scripts application
• Don the Console appender in Automation Scripts application
• Eon the automation script in Automation Scripts application

• A
  1% (1)
• B
  79% (54)
• C
  6% (4)
• D
  13% (9)

Explanation

In IBM Maximo, the logging level for an Automation Script must be configured in two separate locations because the framework requires both a system-level logger registration and a script-level declaration. Option B is correct because the Logging application contains a dedicated autoscript logger that must have its level set (e.g., DEBUG, INFO) to enable log output at the system level. Option E is correct because the individual script record in the Automation Scripts application also has a logging level field, which controls verbosity for that specific script.

Why the distractors are wrong:

• A - The Console appender controls the output destination (where logs are written), not the logging level; it lives in the Logging app but is not where you set the autoscript log level.
• C - There is no standalone "Logging" section within the Automation Scripts application; the level is set on the script record itself (that's option E).
• D - The Console appender belongs to the Logging application, not the Automation Scripts application.

Memory tip: Think "two apps, two settings" - one in the Logging app (register the autoscript logger) and one in the Automation Scripts app (configure the individual script). If either is missing, logging won't work as expected.

No community discussion yet for this question.