HCL Domino Ideas Portal
Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
would this be for all agents? just in troubleshooting situations?
there is existing logging for all agents including the runtime in ticks
Settings
set config log_agentmanager=2
Enable Debugging (also needs the log option)
tell amgr debug r
Disable Debugging
tell amgr debug off
(also set back the log_agentmanager variable)
After enabling your log should contain agent-manager log-output like this
>17.06.2004 10:28:22 AMgr: Agent 'TestAgent' in 'agent.nsf' ran successfully; elapsed time was '1003' ticks
It seems many developers all say the same thing: if you want to know when an agent finishes, write the code into the agent. Consider that every other server task reports when it starts and finishes processing something, e.g. Compact, fixup, replication, mail routing. For some reason AMgr didn't get the memo. It just notifies when an agent starts, but not when it stops. It would be much easier to make Amgr run like all the other server tasks rather than create the work-around in every agent.
Of course you can let the agent (LS of Java) dropping a finished message to the log.
But I agree, it's somewhat inconsequential to have a started, but not a finished message.