Link

Log Insight 3.3.1 Available Now!

Today, Log Insight 3.3.1 was released. This minor maintenance release was primarily to address an agent instability found. An upgrade for the agent and server are provided. Anyone leveraging a Log Insight 3.3.0 agent are encouraged to upgrade. For more information, see the release notes. The resolved issues listed are:

  • The pre-installed Log Insight agent inside the Log Insight virtual appliance is automatically configured with an invalid hostname by default.
  • The vRealize Log Insight agent may unexpectedly exit after 4-7 days of uptime on some Linux platforms.

Also note that vRealize Suite 7 was released today and it includes Log Insight 3.3.1.

li-logo

Link

Log Insight 3.0 Announced!

I am not sure if you caught the press release this morning, but Log Insight 3 (3.0 — was called 2.6 during the Tech Preview period) has been announced! Expect to here more this week at VMworld, but what is posted now is:

vRealize Log Insight™ 3 – New features in vRealize Log Insight 3 will include double the scale and performance to 15,000 messages per second, improvements in fault tolerance around clustering, analytics improvements with new charting options and query snapshots, improved integration with vRealize Operations, and improvements in Big Data style query execution.

While I cannot talk about specifics now, doubling the performance will be huge for many users, the fault tolerance improvements will be a welcome addition to those in production, the new charting options will be root cause analysis even easier and the improved integration with vR Ops is really, really cool.

In addition to Log Insight 3.0, vR Ops 6.1, NSX 6.2, VIO 2.0, SRM 6.1, vSphere APIs for IO filtering, and a Tech Preview of Project Skyscraper were all announced! Be sure to check out the entire press release here. More information is also available on the media kit.

Link

Log Insight: Converting from EPS to GB and Back

As many of you know, I have a calculator for Log Insight that makes it possible to properly size an environment as well as determined the network and storage utilization required to support the environment. I have been asked on multiple occasions how to convert Events Per Second (EPS), a metric Log Insight leverages, to storage utilization in GB, a metric that storage administrators care about, and vice versa.

To handle this conversion, I have added a new table to the calculator, which allows you to either specify:

  • EPS calculated by [Day|Month|Year] and convert to storage utilization in GB (purple)
  • Total events and convert to storage utilization in GB (blue)
  • Average storage utilization per day in GB and convert to EPS (green)

To understand what inputs are needed for which conversions, I have color coded the inputs and the outputs and listed the color in parenthesis above. Note that for all calculations, the average event size in bytes is needed. I have added help text to that input, but to reiterate here:

Enter a number between 0 and 10000. Note that the average event size for Windows events is 220 bytes and the average for all other events is 170 bytes. If you are unsure of what to enter, 200 bytes is typically the best option.

Please try out the calculator here and let me know what you think!

li-logo

Link

Top vBlog 2015 – Please Vote!

It is that time of the year again: Voting for the Top vBlogs of 2015! What is it? It is a survey asking you to select what you believe are the top 10 VMware and virtualization blogs. I would like to thank Eric Siebert for organizing the annual event and Infinio for sponsoring the survey in 2015.

Last year was the first year I requested my blog be entered. My focus for the last year has been around VMware management products and specifically Log Insight. I hope you have enjoyed and found value in the content and I would greatly appreciate your consideration during voting this year. There are a ton of quality blogs out there and over 1400 represented in this survey; I encourage you to look into as many as you can.

When voting, consider the following aspects:

  • Frequency (how often they post): I blog three times a week.
  • Quality (how well the posts are): I will let you decide 🙂
  • Length (how long the posts are): My in-depth technical posts are typically 800 word while most other posts are typically 300 words.
  • Longevity (how long they have been blogging for): I have been blogging since 2009 and my first post on SFlanders.net was in 2011. I have been blogging about Log Insight since it was first announced.

Note that the above considerations are suggestions. I would encourage you to vote for blogs that have been helpful to you over the past year. Please take the time to fill out the survey and thanks for your consideration: http://www.surveygizmo.com/s3/2032977/TopvBlog2015

topvblog20151smallest