Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Kiwi Syslog Server > Kiwi Sys - Knowledgebase Articles > Kiwi Web Access Performance

Kiwi Web Access Performance

Table of contents

 April 25th, 2016

Overview

This article provides brief information and steps to avoid Kiwi Syslog performance issues and database corruption with web access.


Environment

  • Kiwi Syslog versions earlier than 9.4.2

Steps

Reconfigure the Kiwi Syslog Server to limit what it inserts into the Kiwi Web Access database to syslog message with a priority of Warn or higher. As such, the SQL CE database will grow at a manageable pace.

  1. Log in to Kiwi Syslog Web Access.
  2. Go to the Admin tab. Under Database Maintenance decrease the maximum size of the database.
  3. Go to the Settings page. Under General Settings decrease the number of rows per page to 25 rows or less.
  4. Decrease the amount of data you are inserting into the database by adding filers to the same rule that contains the Log to Kiwi Web Access Action.
  5. Decrease the database size.

 

Recommendations:

  • Log device syslog messages to separate directories based on the source.
  • Reduce the number of Rules/Filters/Actions you had, as some proved to be unnecessary.

 

Note: If you are running on a version earlier than 9.4.2, there is a known issue about CPU usage and session timeout and it is fixed in Kiwi Syslog Server 9.4.2. See the Release notes for version 9.4.2 for more information.

 

 

Last modified

Tags

Classifications

Public