• Exception monitoring in AVIcode 5.7

    This article discusses the general exceptions monitoring configuration including “All Exceptions†/ “Critical Exceptions†check box, Exception Tracking and Exception Handlers options explanation.

    Read more: Exception monitoring in AVIcode 5.7
  • Collecting custom performance counters with AVIcode 5.7

    This article covers questions over how to configure custom counters collection and where you can check out them in SEViewer as well as how to transfer counters to Advisor in order to make them available for AVIcode reports.

    Read more: Collecting custom performance counters with AVIcode 5.7
  • Grooming in SEViewer and Advisor

    Grooming is optimization feature intended to limit number and storage terms of events and performance counters in AVIcode DBs. Having read this article you will learn how to configure grooming for both SEViewer and Advisor.

    Read more: Grooming in SEViewer and Advisor
  • Heavy / Light optimization part II. Self monitoring and Back To Light

    The current article will shine a light on “self monitoring” configuration aspects as well as continues and extends article over Heavy / Light Optimization Logic.

    Read more: Heavy / Light optimization part II. Self monitoring and Back To Light
  • AVIcode Database Maintenance Essentials

    This article lists 5 things you need to include into your database maintenance plan for AVIcode. It covers the most important aspects of AVIcode Databases Maintenance including statistics update, indices reorganize/rebuild, database integrity verification, database backup/restore and cleaning up old and historical data from msdb database.

    Read more: AVIcode Database Maintenance Essentials
  • Light Requests Optimization Logic. How does it work?

    “Light Requests Optimization” in AVIcode is perhaps one of the most complicated subjects. We get questions about it all the time. Today we will take a look under the hood of the AVIcode Agent and will discuss how exactly “Light Requests Optimization” works.

    Read more: Light Requests Optimization Logic. How does it work?