CategoryNetwork Insight

Transferring Applications between vRealize Network Insight instances

Let’s say you have multiple vRealize Network Insight instances. Maybe a staging instance for trying new searches, alerts, or other configuration – and a production instance. Or you’re migrating from an on-premises instance to a vRealize Network Insight Cloud instance. Or you just want a backup of the hard work you put into curating the applications. As with many things; there’s an API and script for that!

Python SDK & Examples

The Python SDK is a library generated automatically by the OpenAPI specification that vRealize Network Insight has baked in. In addition, it has a ton of example scripts that … Read more

Integrating vRealize Automation Cloud & vRealize Network Insight Cloud

When you have vRealize Automation in place to deploy applications, vRA is the source of truth when it comes to the application landscape. It makes sense to treat it that way, and not have other products (like vRealize Operations or vRealize Network Insight) have to discover those newly deployed applications on their own. Which is what this post is about!

Before you continue, I’ll not be going too deep into vRA, vRNI, or the Extensibility in vRA that makes this happen and assume you know the basic of those products and features. This post explain how to get your vRA … Read more

vRealize Network Insight Cookbook Update

It’s been a while since I posted about the vRealize Network Insight Cookbook. Honestly, the pandemic and other events over the last two years drained my creativity, especially in writing. The goal was to update it with new features every six months, and add more of the big ticket items (like SD-WAN, Network Assurance and Verification) continously. More than a year and a half later, I can say that that plan failed. 🙁 

However! My writing creativity seems to be getting back to some resemblance of what it was and I’ve started updating the digital cookbook. 🙂

Cookbook Updates

Read more

Event-Based Automation with vRealize Network Insight & VEBA

With the release of vRealize Network Insight 6.4 – something awesome was added: the databus. In its essence, the databus is a feature that exports data out of vRNI using REST API webhooks. These webhooks deliver the data over HTTP[S] to an endpoint that can then parse and process the data. There are several message groups, which you can subscribe an endpoint to. The message group decides what type of data is exported and with the initial databus feature, you can subscribe to: Application updates (newly discovered, updated, or deleted apps), and Problems (alerts). The latter open up event-based … Read more

Natural Language Searches with PowervRNI

vRealize Network Insight 6.3 brought a new API endpoint: /search/ql. The QL stands for Query Language, which is the same language that’s used in the search bar. I added support for that endpoint in PowervRNI 2.0 with the cmdlet Invoke-vRNISearch. With this post, I’d like to explain why that’s the best since sliced bread. 😉

Previously, there was the /search API endpoint, but that used an internal query language. You would run a search in the vRNI interface, open up the browser Developer Tools and look for the internal query that went against the vRNI backend. You could … Read more

Securing Platform Communication in a vRealize Network Insight Cluster

Hi there! It’s been a while. How are you doing? In the last release of vRealize Network Insight, version 6.3, there’s a new feature called Secure Cluster Communication. By default, the communication between Platform and Collectors is encrypted via TLS. A Platform cluster, has a few data replication services (FoundationDB, Kafka,  running between them – which are not all encrypted by default. The Secure Cluster Communication feature allows you to set up VPN tunnels between the Platform nodes and encrypt all traffic going between them. 

It’s not recommended to split Platform nodes between different locations. But, if you do … Read more

Adding a second network interface to a vRealize Network Insight Collector

Sometimes networks are so firewalled off that you need management appliances with 2 network interfaces to manage the devices inside the quarantined network. This is sometimes true for network device management, where there’s no way to connect to the switch, router, firewall, or load balancer over the regular network and a jump host is always needed. If you want to monitor them, the monitoring appliances would have 1 interface in the quarantined network and 1 interface in a network where it can be accessed by admins. While it’s a different discussion about whether that’s safe or not (compromise the monitoring … Read more

© 2024 Lostdomain

Theme by Anders NorénUp ↑