darryld ✭✭✭✭✭

Eye Of The Storm?!! Thats a horror from my past. The company I work for used to resell it but we gave it up in favour of Solarwinds, but that was 5 years or so ago so it may have changed a lot since I last looked at it. It was difficult to configure and maintain back then

Add the Edit Custom Properties resource into their Node Details view

In my experience it is not the database as a whole which increases in size but one table. As you are collecting traps check the size of the trapvarbinds table. You may need to restrict the number of traps you are receiving or us the "discard" action to limit the number which are stored in the database

what does the web site show when the map is missing?

If I remember correctly the configflag property needed to be created to allow config files collected using early versions of Cirrus to be viewed in Orion's web console

The definitive guide would be the relevant rfcs 1155, 1156 and 1157 if I remember correctly. They are at www.faqs.org/rfc

I also think this is a feature that should have been left as it was. Not too keen on the changes to Node Management either

If you are happy that these values are "normal" for the devices in question then yes I would filter them from the original alert and create a new one just for them

Sorry I don't know how to solve this but I have seen it across a range of installations using previous versions of NPM as well as the latest. When I saw your post I was hoping to find the solution