Start/notes.ini Parameters/Log_AgentManager

Log_AgentManager

Parameter: Log_AgentManager
Short description: Permanent operational logging of the Agent Manager — sets in the form 0 (off) | 1 (only run start) | 2 (start + end) which agent activities are logged in 'AMgr' events of log.nsf and on the console; the standard switch for permanent agent monitoring (in contrast to the temporary, more detailed Debug_AMgr).

Profile

Parameter
Log_AgentManager
Category
Logging / Debug (Agent Manager)
Available since
At least 9.0.1 (HCL docs 9.0.1 – 14.5.1)
GUI equivalent
No direct GUI — alternatively maintained in the Configuration Settings document → NOTES.INI Settings tab
Possible values
0, 1, 2
Default
None (HCL: no explicit default — behavior like 0)

Description

According to HCL product documentation (14.5.1, Log_AgentManager):
Specifies whether or not the start of agent execution is recorded in the log file and shown on the server console.
Syntax: Log_AgentManager=value
Description: Options for value are:
- 0 — Do not log agent execution events
- 1 — Log agent execution events (partially and completely successful)
- 2 — Log agent execution events (completely successful only)
Applies to: Servers — Default: None — UI equivalent: None, although you can specify this setting in the NOTES.INI Settings tab of the Configuration Settings document in the Domino® Directory.
With Log_AgentManager, the Domino server writes a log entry to the server log (log.nsf, AgentLog view) and outputs a console message at the start of each agent run. The parameter is the classic choice for Agent Manager diagnostics and performance audits — e.g. to see which agents are triggered when by which user, or to check scheduled agents for runtime issues.

Example configuration

Log only completely successful agents (lower log load):
Log_AgentManager=2
Log all started agents (more comprehensive, more log volume):
Log_AgentManager=1
Disable logging entirely:
Log_AgentManager=0

Notes & pitfalls

  • HCL specifies no explicit default — the behavior without the parameter corresponds in practice to 0 (no Agent Manager logging).
  • Value 1 covers both partially and completely successful agents — 2 filters out the partial successes and shows only clean runs.
  • For detailed tracing of an individual problem, Debug_AMgr is more useful — Log_AgentManager is more suited for persistent operational logging.
  • The Configuration Settings document takes precedence over notes.ini if both set a value.
  • Only takes effect for agents executed server-side by the Agent Manager — web/HTTP agents (-WebAgent workflow) must be observed separately via HTTP logs.

Sources (HCL Product Documentation)