search cancel

How to throttled back "Critical Error - Failed to insert QoS data" from being sync'd to ServiceNow

book

Article ID: 215141

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

snmpgtw 1.40 configured with a Webhook for ServiceNow Event Manager with one NAS AO enabled.

The following data_engine critical errors are generated on a daily basis where they clear themselves within a minute.

Per the article below, these alarms are expected during the data_engine maintenance but need to prevent them from being sent to ServiceNow Webhook.

What is the Meaning of the alarm: Insert bulk failed due to a schema change of the target table
https://knowledge.broadcom.com/external/article/34364/what-is-the-meaning-of-the-alarm-insert.html

Cause

NAS Auto Operator not configured properly

Environment

Release : 20.3

Component : UIM - DATA_ENGINE, UIM - SNMPGTW

Resolution

1. Add a second NAS AO for the snmpgtw ServiceNow Webex hook for data_engine alarms with 'On overdue age' set to 2min

2. After adding the second AO, deactivate/activate both the snmpgtw and nas probe

4. Validate that ServiceNow alarms sync is working

5. Monitor data_engine alarms and confirmed that they are NOT synced to ServiceNow