1 Reply Latest reply on Sep 15, 2016 3:18 AM by jhynds

    Agent Event Caching and Delivery to Manager


      We've had some issues recently in which we've discovered that no events have been collected for a period of several days, but the manager is up and running as far as we can tell. The issue appears to have been resolved by upgrading to v6.3, however it's raised the following questions regarding how the agents on our Windows servers process collected events.


      1. Will the agent cache events if it cannot connect to the manager and, if so, what parameters are available for controlling the number of events that are cached and/or the time period that these are retained for?
      2. Is there a specific Internal event that would indicate that the agent is seeing the manager as online and available and is therefore sending its collected events, but they are never being written to the database? (This is what I suspect was happening in our specific situation.)


      Thanks for the help.

        • Re: Agent Event Caching and Delivery to Manager

          Hi afiore,


          curtisi provided some information in this thread that may be helpful: Agent Cache Size


          I'm not aware of any specific internal events to capture the scenario mentioned in point #2, but I would certainly recommend keeping an eye on Internal Alert/Error/Exception/Warning if/when this happens again. If it happens again I would also recommend raising a technical support ticket & they could capture & analyse manager/agent debug logs which may provide some clues also.