I have been asked a few time how to mass deploy the Log Insight Windows agent and thought I would share this documentation link, which…
I cannot remember the last time I burned a CD or DVD. I can remember the last time I attempted to create a bootable USB device from an ISO. Unfortunately, I have memories of wasting time creating bootable USB devices as well. In this post I will discuss how to use UNetbootin to make creating bootable USB devices easy.
The Log Insight agent can be configured to monitor log files within specific directories. It is important to understand how and when the agent detects directories and files in order to ensure that events are monitored and collected properly. In this post, I will discuss the differences between how the agent handles directories versus files.
When the Log Insight Windows agent was released in version 2.0, the decision to use the agent was easy because Windows does not natively support syslog. Given the release of the Log Insight Linux agent, I have been asked a few times why the agent should be used over already available syslog agents like Rsyslog and Syslog-NG for sending events to a remote destination like Log Insight. I would like to cover 12 reasons in this post.
My post on vCAC logging has been quite popular since its release. With VMware’s release of new and updated management products at the end of 2014, some changes to vCAC, now vRA, exist. In order to avoid confusion by attempting to update the older post, I decided it was time for a new post. Also, with the release of the Log Insight Linux agent, it is a good time to show end-to-end remote logging for vRA when leveraging the Log Insight agents.
Unfortunately, vRA still does not support setting a remote syslog destination to forward all vRA logs within the GUI yet. Like last time, I would like to cover where all the log files are located and more importantly how you can forward them to a remote syslog destination like Log Insight.
In my previous post, I discussed how to build Log Insight Windows agent configuration sections for monitoring log files, in this post I would like to provide some additional sample configurations for common Microsoft and VMware applications. I will be updating this post over time so be sure to check back from time to time!
A covered how to configure the free Log Insight Windows agent when the Log Insight 2.0 beta was released. Since the agent’s announcement, the demand for the agent and the appropriate configuration has increased daily. The most common request I have received to date is, “how do I monitor logs for product X using the Log Insight Windows agent?%#8221; In this post, I would like to take a deeper look at the filelog configuration option of the agent and how to approach building configuration sections.
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!