Welcome back to the next installment of our weekly update in which we do something a bit odd for a vendor: expose holes in our product! Let’s be honest: nothing is perfect — and by discussing problems netTerrain users have encountered, we want to foster a collaborative environment, share some workarounds around common issues and — why not, poke a little fun at ourselves.
For this week, I will touch upon netTerrain’s Integration Toolkit (ITK). We have been getting some requests and questions around it and in general our response has been tame. There is a specific reason for this, and you may have already seen it in previous blogs: we are scraping the ITK for the interim.
Here’s an example of a customer question: last week we had a customer wondering if certain auto-layout functions could be expanded in the ITK, and we said no. The reason for this is that development of the ITK is frozen now and all efforts are now being directed towards the vastly improved Collector (as you may know, we are constantly improving netTerrain as our goal is nothing less than putting out the best DCIM, OSP, and Network Mapping solutions on the market today.
Why vastly improved?
Well, citing a previous blog, allow me to regurgitate some of the reasons we believe the Collector is the way to go:
As you can see from the list above, these are some massive improvements over the architecture of the ITK and come with a much better set of discovery capabilities.
Having said that, there is one big piece still missing (which is what will eat up the bulk of the migration efforts in the next 12 months): the ability to create custom connectors to any data source. What can you do?
Well, for starters the ITK isn’t dead. You can still use it for automatically generating IT and network mapping diagrams. And, until you can fully replace it with the Collector we still provide full support for it.
What about new features? As I mentioned, we are not developing it anymore, however specific features that are more discovery-related can be accelerated in the Collector (which encourages you to migrate).
Finally, there is the lovely API! It is a powerful tool that can supply features such as the question this customer had. Using the SOAP or REST API you can take any data already in netTerrain and supply your own positioning algorithms.
In sum: the ITK isn’t gone — it’s just frozen for development since a much better Collector is replacing it in the next 12 months or so. In the intervening months, however, we will continue to provide full support for tickets and issues and we can help you navigate the API to supply any specific features for connector-related tasks that need more immediate attention!
Stay tuned for our next installment in this ongoing series — and, in the meantime, if you need support: give us a shout.