From time-to-time, I receive a question asking what the current retention period is for a LI instance. In this post, I will discuss how Log Insight handles retention and how you can determine the current retention period.
In this post, I would like to dig a little deeper into my second attempt to become fit. Specifically, I would like to focus on four areas of my journey:
In part one of my series on vRealize Hyperic deployment and configuration, I discussed an overview of the Hyperic components, downloads available, deployment options, and upgrade procedure. In this post, I want to discuss configuration of the various Hyperic components.
In my last post, I talked about the differences between how events are displayed over the syslog protocol, which has a strict format structure, and the ingestion API, which sends events as-is. In this post, I would like to talk about the differences between using the syslog protocol versus the ingestion API when it comes to the Log Insight agent and the Log Insight forwarder.
As you know, Log Insight introduced an ingestion API with the 2.0 release. This ingestion API can be used by anyone, but is leveraged by default by the Log Insight agent available for Windows as of 2.0 and Linux as of 2.5. The ingestion API is powerful because it provides functionality beyond what the syslog RFC defines, but it is important to note that events received over each protocol may look different. Read on to learn more.
Copy and paste are two commonly used commands for almost all computer users. One complexity of the copy command is whether or not formatting should be included with the text/images selected. WordPress understands this dilemma and offers an option to clear formatting. In this post, I will discuss the importance of the clear formatting option and why it should be used.
I just concluded a three part series on how to backup and restore Log Insight. I just realized that I missed how to backup and restore the SSL certificate on the Log Insight virtual appliance. I will address this oversight in this post and then update the previous posts.
As you know, Log Insight is primarily used through its HTML5 interface. By default, Log Insight ships with a unique SSL certificate per appliance. The Administration section of the Log Insight UI allows a user to upload a PEM certificate to use in place of the self-signed certificate. In this post, I would like to discuss operations you may desire to perform in regards to SSL in Log Insight as well as share a script on how to properly manage all the available options.