Skip to Main Content
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

Status Needs Review
Workspace Domino
Created by Guest
Created on May 7, 2025

Make Agent Manager report when an agent ends.

Agent manager reports when an agent starts:

05/06/2025 12:21:21 AM AMgr: Start executing agent 'Testagent' in 'MyDatabase.nsf' by Executive '4'

But it doesn't report when an agent ends. If it did, it would be very helpful in troubleshooting problems. Other tasks all report when they are done (e.g. replication, compact, mail router). Why not AMgr?

Yes, agents can be modified to write a message to the log, but that would require me, an admin, touching every agent on our server.

Please modify Agent Manager to report in the log.nsf when an agent ends.

-dh

  • Attach files
      Drop here to upload
    • Guest
      May 17, 2025

      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


    • Guest
      May 7, 2025

      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.


    • Guest
      May 7, 2025

      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.