Skip to content

Month: August 2014

Introducing VMware vRealize!

To date, VMware has had two primary brands being vCenter and vCloud, however many products did not technically fall under one or the other. A big announcement today prior to the start of VMworld US 2014 is that all of VMware management products are being rebranded under the name vRealize as well a renaming of several management products. This impacts products including vCAC, vC Ops, and of course Log Insight.
keep-calm-and-vrealize-4

Introducing the VMware EVO Family!

When it comes to infrastructure, VMware provides choice to its customers. To date, this has either been a “build your own” model or a converged infrastructure with something like VCE, VSPEX, or FlexPod. Today, prior to the start of VMworld 2014 US, VMware announced a hyper-converged infrastructure that offers faster time to deployment and a simplified SDDC management lifecycle.
evo

Log Insight Calculator

A get a lot of questions around Log Insight calculations including how large to size a Log Insight instance/cluster, how much storage is necessary to meet retention requirements, and how much network bandwidth is used. I typically point people to the Log Insight getting started document, but this only provides part of the information and also requires manually calculations to answer all the common questions. As such, I have put together a Log Insight calculator!
SAMSUNG

Using Load Balancers in Transparent Mode – A Workaround

In my last post, I talked about two routing modes used on load balancers: NAT and transparent. As you may recall, I recommended against using transparent mode unless it is a common practice to use a load balancer as the default gateway in your environment. In this blog post, I would like to provide another workaround that would enable transparent mode without having to point the default gateway of your Log Insight nodes to the load balancer!
enet-loopback

Log Insight Cluster: Data Not Balanced Across Nodes

In Log Insight 2.0 a scale-out feature was introduced. The best practice when using scale-out is to configure an external load balancer in front of the cluster and send all ingestion traffic (i.e. syslog and ingestion API) to the load balancer instead of directly to a node. The reason for this best practice is to assist with balancing data across nodes and also to provide ingestion high availability. In this post, I would like to discuss why data may not be balanced across a Log Insight cluster whether a load balancer is used or not.
unbalanced_scale

Heads Up! Updated Microsoft Content Packs Now Available

As you may have seen on the VMware Management blog, I recently announced updated Microsoft content packs for Log Insight. For those that are currently using either the Microsoft Windows or Microsoft Active Directory content packs, I would highly encourage you to upgrade and for those using the Microsoft Exchange there is an update for you as well. Read on for more information!
series-heads-up