Indeni: There’s More To A Name Than Meets The Eye

When you visited today you likely noticed a change. We updated our company identity and the Indeni logo to better represent the value we provide to our customershappiness.

We believe that successful companies are created by happy people. 

When you are happy, you are more productive and can propel your business forward. This goes for the employees that work at Indeni as well as the partners and customers we serve. With that said, creating happy employees isn’t easy, especially in Information Technology.

There are a number of reasons why it’s difficult to be an IT professional today.

  • The number of hardware solutions to support an Enterprise is off the charts.
  • Networking and data center operations are moving to the cloud.
  • IoT products are becoming a must-have to differentiate from the competition. These solutions create an even greater reliance on network availability and the infrastructure supporting it.

Combine the changes in the technology landscape with not having enough time to invest in their professional development, it’s no wonder employee satisfaction in IT is at an all-time low. There are over 250,000 jobs open in the US alone for Network Operations.

indeni logo update

Our Founder saw the need for a change back in 2009, as Network Engineers and Administrators struggled to balance the day-to-day operations; canceling meetings and pushing projects to move to the most urgent task at-hand. That same premise stands true today as the number of devices and the data they generate is growing at an extreme pace. Now more than ever before, it is important for IT operations professionals to spend their time well, and we have designed Indeni from the ground up to enable this.

Three ways Indeni enables IT to spend their time well:

  • Crowd-sourced learnings. We aggregate lessons learned from your peers and provide them to you as needed through our platform in the form of human readable notifications. This knowledge is collected from the device manufacturer, our customers, and power users of those devices from around the world. View example Indeni notifications for Check Point, Palo Alto Networks, F5, and Cisco.
  • Automation. We remove the manual task of running scripts and queries to troubleshoot and identify the root cause of performance degradation or downtime. Out-of-the-box Indeni knows what to investigate and runs the appropriate commands to inspect the device and find the answer.
  • Analysis. We compare the data collected from your devices within your environment across logs, configurations, and other granular metrics only accessible through a non-SNMP connection. The internal and external correlation of these attributes, within your environment and against the data of the Indeni customer base, allows us to reduce noise for IT. There are hundreds of network monitoring, security incident, and configuration management solutions that will send you alerts. We believe it’s not the volume, but the accuracy and actionability of those alerts that will make every individual IT professional more effective.

Our colors are a constant reminder of our purpose

Similar to the creators of Wi-Fi, we thought the name of Indeni sounded quite cool. You can see how we arrived at “Indeni” through a combination of coding and scripting here. Our colors however have a few symbolic meanings: 

  • Blue = Relief. We want you to have a sigh of relief when using Indeni. We’ll find issues you didn’t know you had and give simple instructions for how to fix the problem fast.
  • Green = Reuse. We work with some of the best and brightest IT professionals, as you have over the course of your career. It’s the combination of their education and experience that makes them so valuable. We believe the only way to solve the challenges that present themselves at each stage of the IT lifecycle is to collaborate with other IT professionals.
  • Smile = Happiness. Can you see the smile in our logo? We hope that by using Indeni you and your customers are able to do this more often.

Are there ways we can increase your happiness as a customer or partner? Let us know by commenting below or contact us here.


Join @indeni Tweet Sweep at CPX 2017

 Tweeting for prizes for CPX? Yes, please!

indeni is thrilled to participate in our fifth consecutive year at Check Point Experience (CPX). As one of the major firewalls indeni covers, we love connecting with the Check Point community year after year. In order to connect with each of you, we are kicking off the @indeni Tweet Sweep to open up the conversation even before CPX! Tweet at @indeni your answers to the weekly questions posted on our Guide to CPX and collect your prizes at our CPX booth!

@indeni Tweet Sweep of the Week:

What was your favorite CPX + indeni memory

from CPX 2016 in Chicago?

How can you participate?

Did you say prizes?!

  • 1 tweet = 1 indeni sticker
  • 3 tweets = 1 indeni T-shirt
  • 10 tweets = WIN A DRONE!
           (While supplies last)

How do I get my prizes?

  • Stop by our booth at CPX
  • Show us your tweets
  • Claim your prizes!!

Q: I am having trouble thinking of good tweets…

A: No Problem! Here are some ideas for this weeks Tweet Sweep:

  • @indeni I realized what it means to be truly proactive. Preloaded knowledge running around the clock versus a red light/green light. Thanks
  • @indeni I spoke with indeni’s CEO/founder, @yonadavl, about indeni’s knowledge around VPN Tunnels & expired contracts. Exciting work!
  • @indeni I took a selfie with the indeni team!
  • @indeni  who knew indeni could alert me to expiring licenses, learned that in their demo at CPX
  • @indeni  in a sea of blue smiley faces lies a change in how security and operational teams look at their environment.
  • I saw a great live demo at the @indeni  booth…the smiley face t-shirt was a great bonus, too!
    (Feel free to share a photo of you wearing your T-Shirt!)
  • @indeni the Nerf Guns still crack me up
  • Got drinks with @indeni  after day 2. The team is very knowledgeable and dedicated to their smiley face shirts!
  • @indeni  made the expo floor fun and stimulating. I am looking forward to seeing what they do this year!
  • @indeni  I spotted the indeni team at a Happy Hour by their Smiley Face T-Shirts. Great talking to a fun group of people!

In conclusion

CPX is 6 weeks away but the fun can start now! Check back for next week’s tweet of the week.

Good Luck!

Check out our Check Point solutions here.

How to monitor F5 devices – SNMP vs API vs SSH

F5 has many ways of interfacing with their products and when writing monitoring we had to do some research which one is more suitable in terms of performance. After all, monitoring should not harm the device it monitors. When choosing methods we looked into iControl REST, SNMP and TMSH. See below for how this test was conducted and which one won.

The best way to monitor F5 – How the test was conducted

We ran each type ~20 minutes continuously through command-runner. While running the tests the web interface was used to make sure that the web interface responsiveness was up to par.

The commands to run each test

while true; do full-command –basic-authentication user,password rest-pool-statistics.ind
while true; do full-command –ssh user,password ./show-ltm-pool-detail-raw-recursive.ind
while true; do full-command –ssh user,password ./snmp-pool-statistics.ind


The test started out with 283 pools (with 200 additional ones created just for this test). However, when trying the tmsh command, command-runner timed out, so we had to reduce to the original 83 pools and rerun the test using rest to make it fair.

  • Test 1: REST = 283 pools
  • Test 2: Tmsh = 83 pools
  • Test 3: SNMP = 83 pools
  • Test 4: REST (take 2) = 83 pools

4 hour graph

24 hour graph for reference


  • Did not produce any timeouts in the GUI in any of the two tests.
  • Always produced results.
  • Management interface only became sluggish one time during the second attempt. Most likely because of the already high swap usage created by the TMSH tests.


TMSH produced these once in awhile:

  • When that happened you can see the gaps in the graph. It is unknown what the gap after the graph was because we was working on the snmp metrics at that time.
  • TMSH also failed to give results sometimes.
  • Forced to run with fewer metrics than rest in order to even get a result.


  • Truncated the pool names sometimes. It is unclear why ast was always done on long names, but different lengths.
  • Did not produce any timeouts in the GUI.
  • Always produced results.
  • Did not have as many metrics as REST since the exact same metrics was not available in one command (pool state and availability is missing).
  • Management interface became a bit sluggish on and off.


Over all REST won the test with SNMP as second. TMSH did not even qualify as it takes up very large amounts of memory and swap which negatively affected the overall system.

Thank you to Patrik Jonsson for contributing this article.