What We’ve Learned From Speaking With Our Customers

Key takeawaysThis key takeaway was generated through LLMs crawling the page and coming up with an overview of the content.

The article summarizes a customer survey conducted by indeni in early 2016 with dozens of primarily large-enterprise customers, capturing feedback on product fit, support, device coverage, proof-of-value trials, and roadmap priorities. Respondents value indeni's unique proactive, deep-inspection approach to device integrity and monitoring, praise support responsiveness, and report measurable operational improvements (reduced surprise calls, improved uptime), while calling out UX, debug data collection, expanded device support, APIs, alert correlation, and reporting as improvement areas. indeni plans product changes including new UI, API additions, expanded device support (Cisco Nexus, BlueCoat), and easier update/diagnostic workflows to address customer requests over 2016 and beyond.

What were the main reasons customers decided to purchase indeni and how did proof-of-value trials influence deployment?

Customers most commonly cited proactive monitoring, increased visibility, and specific outages that indeni could have detected as primary purchase drivers. Many respondents emphasized that the proof-of-value (POV) process was critical: running indeni in trial allowed teams to demonstrate what the product does that their existing tools could not, justify the purchase to stakeholders, and accelerate rollout after purchase. Several customers reported indeni replaced SNMP-based tools after a successful POV, highlighting the trial as the decisive factor in understanding behavior and operational value.

What operational benefits and pain points did customers report from using indeni?

Customers reported clear operational benefits including fewer surprise calls, reduced downtime, and improved uptime—one customer explicitly said their firewall environment became far more stable and they received far fewer incident calls. Support was generally rated highly (mostly 4s and 5s) for responsiveness and technical assistance. Pain points included difficulty collecting debug information during incidents, a need for improved user interface and reporting to help non-technical stakeholders, requests for better alert correlation to reduce noise, and the desire for more APIs and easier update mechanisms.

Which device coverage and product roadmap items did customers request, and how is indeni responding?

Customers asked for support across a variety of devices where failures cause severe downtime; commonly requested targets included Cisco Nexus and BlueCoat, with Cisco Nexus cited frequently and scheduled for addition in Q2 2016. Other requested vendors included FireEye, Riverbed, and Citrix Netscaler. In response, indeni planned to expand device support over the next two quarters, work on a new user interface slated for late 2016, add more APIs (planned for version 6.0), and improve debug collection and update workflows as part of ongoing product development.

Notice: This blog post was originally published on Indeni before its acquisition by BlueCat.

The content reflects the expertise and perspectives of the Indeni team at the time of writing. While some references may be outdated, the insights remain valuable. For the latest updates and solutions, explore the rest of our blog


A month ago I shared some of our plans for 2016 and mentioned that I’d be speaking with our customers, asking them a few questions. The survey was very successful in my opinion – I spoke with dozens of customers for 30 minutes each and asked them 14 different questions. I would like to thank all of the survey participants for enduring my questions and sharing their honest feedback.

Before I go and present our findings, a few points to keep in mind:

So, to begin with, here are some of the recurring themes from the survey:

More specifically, here is our gathered insight per question asked during the survey:

Other pieces of feedback below. These are unedited quotes that are just worth sharing. I added our response in parenthesis, where appropriate:

We are now taking in all this feedback – on the overall level as well as the more specific points people have made. We’ve already started taking action on the feedback and will continue to do so over the next few months.

Thank you all again for your time. We will continue to do our best to satisfy you in 2016 and beyond.

Related content

Micetro_ Simplify Microsoft DNS_ DHCP_ and Active Directory Sites Management

Modernizing Microsoft DNS and DHCP for Hybrid Active Directory Environments

Learn how to modernize Microsoft DNS and DHCP while preserving Active Directory stability. Reduce risk, improve visibility, and simplify management.

Read more
Three armored figures walking toward a futuristic Las Vegas skyline with pyramids, glowing orb, and "Welcome to Fabulous Las

Your journey to intelligent NetOps begins at Cisco Live

Visit BlueCat’s booth or book a meeting now to learn more about how our solutions can help you build a network that supports constant change.

Read more
Stacked colorful wooden directional arrows on a post by a calm seaside with distant hills and blue sky

Replace BIND and ISC with Micetro DNS/DHCP Server (MDDS)

Tired of patching and manually configuring BIND DNS and ISC DHCP? Discover how Micetro MDDS appliances can replace them for modern DDI.

Read more
Row of orange industrial robotic arms positioned along an automated conveyor belt in a factory setting

Automate it all in Integrity with REST v2 API-first DDI management

Discover API-first DDI with Integrity X by using REST v2 to automate DNS, DHCP, and IPAM for scalable, secure network operations.

Read more