In part 1 of this series I talked about the different pipelines. In part 2, I would like to talk about how retention works. Hint: It does not involve a database and a full disk is normal!
Cloud Architecture and Observability
Month: June 2015
I have been hearing a few questions around the Log Insight system architecture and more specifically how it works. This week, I would like to walk through a few different parts of the architecture to clear up potential questions. Part 1 of this series will talk about the pipelines Log Insight uses.
I often get questions around Log Insight agent configuration. While the options are clearly documented, it can be time-consuming and error prone to construct lengthy agent configuration files. In this post, I will introduce a CLI utility I wrote to make this process easier and less error prone.
I made it a goal in 2015 to blog about fitness. One of the biggest drivers for this decision was so I could hold myself accountable for my fitness. Given this fact, I would like to share a secret…
If you started with Log Insight 1.x or with an environment that a single Log Insight node could handle then you likely are running a standalone node. Upon upgrading to Log Insight 2.x, when ingestion increases above the amount a single node can handle or when business requirements change (e.g. requiring ingestion HA), moving from a standalone Log Insight instance to a cluster may become necessary. While building a cluster, even with an already leveraged standalone node, is very straightforward, there are several considerations to take into account. In this post, I will walk through these considerations as well as the process to perform the transformation.
If you are running a Log Insight cluster then you have probably seen the Status column of the node table available from the Administration > Cluster page. Under normal operating conditions, all nodes should be shown as Connected. In this post, I would like to focus primarily on the Disconnected status including what it means and the logic for triggering it.
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.
We live in a culture that emphasizes all the wrong metrics. Many people have a perception that getting fit includes the number on a scale, the number on a clothing tag and the number on a nutrition label. I propose we de-centralize those numbers as they are not true measures of fitness. In this post, I would like to discuss numbers that do matter.
I have been asked a few times when you may consider having a service account for the Log Insight UI. In general, all activities should be done by an individual user with their own individual credentials. Like most systems, I would advise against the use of the default admin account. There are a couple of scenarios though where a service account can be beneficial and I would like to discuss these scenarios in this post.
I am by no means a full-time software developer, but I find myself from time-to-time needing to dig into some code. While many developers use an IDE, I find IDEs overkill for my use-cases and an unnecessary dependency on my systems. I recently saw a colleague using VIM very similar to an IDE and I become intrigued. With a little help, I got everything setup and now have an easily portable IDE in an interface I frequently use: VIM. In this post, I would like to walk through the steps that were shown to me to get this all setup.
