Skip to content

Month: June 2013

Operations -> Engineering

As part of human nature we tend to find something that we like and stick to it. We are often creatures of habit. While this can be a good thing, it can also be a bad thing. Too often I find people are afraid to make a change. With change comes uncertainty, with uncertainty comes fear, with fear comes…well, that is up to you. I bring this up as I have made the decision to move from Operations to Engineering at VMware. About four months ago, I was approached with an opportunity for change and after much consideration I decided to step outside of my comfort zone and try something new.
In terms of career changes there are several important things I always keep in mind:

Configure Remote Syslog on VMware Products

Many VMware products offer remote syslog functionality, but some do not include all the logs that you may care about. In addition, some VMware products do not support remote syslog (e.g. VMware products like vCenter Server that run on Windows as Windows does not natively support syslog – more on this in a later post). If you are looking to collect logs from VMware products it is important to understand where the log files are located. Below you will find the appropriate log locations for many VMware products. A big thanks to my colleague Michael White for putting together this list and in particular the vCAC information!
VMware_icon_256x

Configuring Remote Syslog on vSphere Using vCenter Log Insight

Now that you have vCenter Log Insight deployed and configured, you need to configure sources to send their log messages to Log Insight. If you enabled vCenter Server integration then you should start to receive log messages, but this is only the beginning of configuring remote syslog sources.

IMPORTANT: Configuring vCenter Server integration does not configure vCenter Server or ESX/ESXi hosts connected to vCenter Server to send remote syslog to Log Insight. For more information continue reading!

Let’s start by going over what Log Insight supports today and what mechanisms it has to configure vSphere devices for you.

Announcing vCenter Log Insight!

Do you use log messages to troubleshoot issues and perform root cause analysis? Have you ever opened a service request with VMware or any other vendor and been requested to upload a support bundle? If you answered yes to the second question then you should have answered yes to the first. What many people do not realize is that log messages typically provide as much information as traditional monitoring tools and are often used by support teams to resolve an incident. In addition, log messages are usually easier to understand than monitoring tools such as SNMP that require you to translate information like those found in MIBs.
Today, VMware announced a new product that allows administrators and executives to get better insight into their environments via log messages. The product is called vCenter Log Insight and it is a log aggregation, correlation, reporting, and monitoring tool specifically tailored for VMware products.
Why would VMware want to get into this market?