NTM and orion integrate DB

One huge catch with integrating for us is we need to be able to filter what interfaces are imported into NPM.  Currently if I try to import an NTM discovery into Orion, it wants to import every node (good) and every single interface of every switch (not good).

We don't have licensing for every single interface on every single switch, and really don't need that.  We need to import all trunk connections and then pick and choose important connections, such as to key servers or devices.

John,

I know this topic is way too old, but I guess, I would like to back the idea of nathan.hejnicki​. I'm actually thinking, perhaps, if you can find a way to make all devices and interfaces already in NPM (meaning already being monitored) be available as an object in NTM, then it would make our maps better looking. Now, we do not have to worry about consistency for all the names and all the devices we want to monitor.

P.S.

I am not currently a user of NTM, but because of the latest requirement in our firm, in competition with the free tool Check_MK, I am actually seriously considering getting NTM (because Network atlas can only do so much). But I am having second thoughts with the idea if we were to build a totally different database than the NPM DB. It double the effort not to mention consistency across two tools working together.

John,

I know this topic is way too old, but I guess, I would like to back the idea of nathan.hejnicki​. I'm actually thinking, perhaps, if you can find a way to make all devices and interfaces already in NPM (meaning already being monitored) be available as an object in NTM, then it would make our maps better looking. Now, we do not have to worry about consistency for all the names and all the devices we want to monitor.

P.S.

I am not currently a user of NTM, but because of the latest requirement in our firm, in competition with the free tool Check_MK, I am actually seriously considering getting NTM (because Network atlas can only do so much). But I am having second thoughts with the idea if we were to build a totally different database than the NPM DB. It double the effort not to mention consistency across two tools working together.