To conclude the series on Log Insight system architecture I would like to talk about the life of an event. This post needed to come last so that the relevant system architecture could be discussed first.
Cloud Architecture and Management
15 search results for "log insight system architecture part"
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 have covered Log Insight event forwarding in the past, but wanted to discuss a potential gotcha when leveraging filters that contain the backslash character. Read on to learn more!
Now that the evolution of topologies and high availability with Log Insight is known, I would like to cover greenfield and brownfield deployments as well as security considerations. Read on to learn more!
Log Insight notifies users when it is unable to maintain the defined retention period by sending a system notification. In this post, I would like to walk through what the system notifications mean in a clustered environment. Read on to learn more!
I covered query building in Log Insight a long time ago. While the UI has changed significantly since I wrote those posts, the information contained within them remains true to the current version of Log Insight. In Log Insight 3.0, two new operators were added to certain places within the UI — in one instance replacing two existing operators. In this post, I would like to discuss these new operators. Read on to learn more!
Depending on how long you have been running Log Insight and how many times you have restarted it, you may notice that the virtual appliance runs a fsck after a certain amount of time. Depending on how much retention you have configured on your virtual appliance, the fsck check could take minutes or hours. In this post, I would like to talk about the configuration of the virtual appliance and why automatic fsck checks are critical.
In my first post about Log Insight 2.5 backup and recovery, I talked about deployment types, backup considerations and architecture of the different Log Insight components. In my second post, I talked about how to backup the various components. To conclude the series, I would like to discuss how to restore the various components.
Can't find what you're looking for? Try refining your search: