Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

update node's name, but alert still trigger old name

syasind

I have updated the name of my devices, node's name in NPM change to the new name, but alert trigger old name.

such as : node's old name A and node's new name B, the node's name in NPM is B , but interface alert trigger A.

please help !

Find more posts tagged with

Accepted answers

All comments

janene16

what alert variables are you using? you can check your DB to see if your node's name has really been updated. I think it's under NodesData table (if you are on NPM version 11.5 or up)

RichardLetts

There is a bug -- the name of the alert object is stored in the database table that keeps count of the number of times the alert has been triggered.

it's not updated if the name of the node chnages, so you end up with alerts on the same nodeidhaving the wrong name on the alert, and confusion when you click on the alert and get an apparently different node (that has that alert on it)

I have not checked if it's still broken in 12.3.

see: Alert Issue (AlertCaption) for a fuller description, and some sqlfixup scripts that I wrote, that come with no warranty...