Kaseya Community

Monitor best practices

  • Hello everybody,

    I'm currently working on a "base monitoring policy" which I can assign to servers and clients to monitor all important and critical events.

    Does anybody of you have a list of things that you monitor because it's very important and critical? E. g. event ids, performance counter etc.

    I don't want to have so much noise in our ticket system which is not important for our team therefore I really want to reduce the amount of monitors.

    I would really appreciate if somebody can share his "best practices" here. Maybe we can then create one nice policy which everybody can use.

    After I wrote down some informations I will post my results here.

    Best wishes


  • I'm going through the same thing myself.  I'm starting with the Standard Solutions Package that Kaseya pulled together and whittling it back to what's important to us.

    Start here > help.kaseya.com/.../index.asp