Beta Feedback

Acknowledge or ignore bad agent events

A customer is monitoring a lot of processes which are known to stay alive for a very short time sometimes. A good example is the iexplorer.exe, which sometimes starts only for 1 sec and then stops.

The aternity agent will try to inject to this process when it gets started, but before the agent is done with it, the process to inject into is already stopped.

The result: an error in the agent event logs, telling "couldn't inject into iexplorer.exe"

which is correct - but it is not an error which the customer should mind

That customer gets such errors very often, and I think there should be a way to acknowledge/ignore them, as they are irritating.

  • Gravatar Fabian Schiffner
  • Aug 15 2016
  • Planned
Type Enhancement
Version Version 8
  • Admin
    Raviv Chalamish commented
    August 16, 2016 18:28

    You are right, there are several events there thatĀ could be considered 'false events'. We will review this feature and consider better way to report about agent events