Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Kiwi Syslog Server > Log Kiwi Syslog Daemon to a MS SQL database

Log Kiwi Syslog Daemon to a MS SQL database

Table of contents

Updated March 11th, 2016

Overview

This article provides steps to log Kiwi Syslog Daemon to a MS SQL database.

The database options are always being improved. It is recommended you download the latest version of Kiwi Syslog Daemon from our SolarWinds Customer Portal

 

If you need details screen shots available under this post Kiwi Syslog logs to store with SQL database setup screen shots

Environment

All Kiwi Syslog versions

Steps

  1. Create a Log to ODBC database action.
  2. Set the DSN name to the system DSN you have created. You can use the browse button to select from the DSNs listed on the system.
  3. Enter a table name that you want to create.
  4. Select the database type from the drop down list. Choose Kiwi SQL format ISO.
  5. Click Create Table. This will erase any existing table and create a new one with all the standard fields.
  6. Click Test to generate a test message. Do this a couple of times.
  7. Click Query Table. This will show you the entries in the table..

You should now be ready to have the messages logged to the database.

 

You only need to use a custom database type if you want to modify the field names or formats. More details on the Kiwi ISO format can be found in the help file.

 

To log to different databases, you will need to use a separate rule, filter and action for each database. You can split the traffic based on host name, or message facility. Just have all the routers send on Local0, all the switches on Local1 and all the firewalls on Local2. Then use priority filters to split the messages.

 

For example:

 

Rule #1
Action: Display (displays all messages - no filters)

Rule #2
Filter: Priority: Local0, all levels
Action: Log to ODBC: DSN=Routers

Rule #3
Filter: Priority: Local1, all levels
Action: Log to ODBC: DSN=Switches

Rule #4
Filter: Priority: Local2, all levels
Action: Log to ODBC: DSN=Firewalls

 

You can either use a separate DSN and database for each rule, or just specify a different table in the same database. The choice is up to you.

 

If you still have issues after following the instructions provided, then please use the Technical Support form to receive further assistance.

 

 

 

 

 

Last modified

Tags

Classifications

Public