Alarm transaction list does not match between nis and sql database

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

When looking at the NAS_TRANSACTION_LOG table in the backend (SQL) database, some transactions are missing for some alarms.

For the affected alarms, the NAS local (SQLite) database.db shows the transactions and they can be seen in the IM Alarm Console History, but the same transactions are missing from the SQL/NiS Bridge database side.

The affected alarms have been transmitted via NAS replication.

For example, an alarm with a count of 100 only shows 2 transactions when we expect to see 100.

Alarms which are sent over queues (not replication) show the full list of transactions in the table.

 

Environment

DX UIM - All Versions
NAS Probe
NIS Bridge Enabled
NAS Replication Enabled

Cause

Configuration

Resolution

On each NAS (primary and remote), add the following (previously undocumented) key/value to the <setup> section of nas.cfg to avoid this problem:

skip_db_insert_on_update_on_replication = no

Adding this key allows the full transaction history of replicated alarms to be reflected in the SQL database.

Note that this will likely increase the network traffic/bandwidth which is consumed by replication and may cause replication of alarm information to take slightly longer due to the increased transactions being communicated across the replication path.