I have used the same vim configuration since college and while it works well, it has become very dated. Recently, I decided to overhaul my vim configuration and thought I would share the results. Read on to learn more!
From time-to-time, I find myself needing to hot add a virtual disk to a VM and expand capacity. While the process has improved over time, I still occasionally run into issues on Linux. In the post, I will cover potential issues and provide a workaround.
I recently attempted to extend a filesystem on my Ubuntu system and ran into an interesting problem I figured would be worth sharing.
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.
In my previous post, I discussed how to configure vRA logging. In this post I would like to provide some Log Insight Linux agent configuration samples for common Linux and VMware applications. You may notice some duplication of information. I will be updating this post over time so be sure to check back from time to time!
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.
For Log Insight 2.5, several enhancements have been made on both the agent and ingestion API sides. I would like to cover these enhancements in detail.
I have received a few comments that while I post a lot of technical information about Log Insight, I do not post a lot of examples and use cases. To begin to address this, I would like to demonstrate how to handle authentication logs, more specific Linux SSH logs, in Log Insight as I recently had someone ask me about this particular use case.
While I do not frequently have the need to create or extend logical volumes, I find that every time I do I need to lookup the commands. To make it easier for myself and others, I have decided to put together the commands I frequently run.