I have spent the last three weeks talking about the new agent parsing feature in Log Insight 3.0. I wanted to wrap-up by discussing why you should use agent parsers.
Cloud Architecture and Observability
20 search results for "agent parsers"
In my opinion, the coolest new feature in Log Insight 3.0 is agent parsers. In this post I will discuss what they are and why they are important.
Now that you know what agent parsers are capable of you are probably wondering how to configure them. In this post, I will start with the basics including the common options for all parsers. Read on to learn more!
I have compared the ingestion API to syslog and also explained why you should use the Log Insight agent, but I have never compared the ingestion API to the Log Insight agent. In this post, I will do exactly that. Read on to learn more!
As you probably know, the Log Insight agent allows you to explicitly include or exclude:
- filelog: log files within a directory
- winlog: Windows event viewer channels
One question I received at VMworld was if you could explicitly include or exclude:
- filelog: certain log messages from within a log file
- winlog: certain events from within Windows event viewer channels
In this post, I will provide the answer. Read on to learn more!
Log Insight 3.3 brings some new features to the Log Insight agent. In this post I would like to cover the improvements. Read on to learn more!
I have received some questions around agent configuration that I wanted to clear up. Read on to learn more!
Now that I have talked about the new agent parsers functionality and walked through each of the supported parsers in 3.0, I want to talk about a new server-side option for agents called agent groups. Read on to learn more!
Now that you know all about the Log Insight 3.0 agent parsers, it is time for a quiz! Read on to learn more.
To wrap up on the parsers, I would like to cover the automatic parser. Read to learn how it works!
Can't find what you're looking for? Try refining your search: