How to efficiently send log data to Google Stackdriver, Part 2

[MUSIC PLAYING] Google Stackdriver is a flexible and convenient way to monitor and manage your cloud-based assets, regardless of where they're located or how they're configured. Syslog-ng delivers the log data critical to understanding what is happening to your IT environment. Whether it's user activity, performance metrics, network traffic, or any other type of log data, syslog-ng can collect and centralize it. You can remove data silos and gain full stack visibility of your IT environment. In this video, join a staff engineer with One Identity's research and development team, as he shows you how to optimize the performance and memory consumption of a syslog-ng Premium Edition, to work efficiently and effectively with Google Stackdriver. Let's do some optimization. I will increase the number of workers and the number of batch lines. Using this configuration, syslog-ng will start eight parallel workers, and every worker will post 1,000 messages as a batch. During the test. I will check the memory and the CPU consumption of syslog-ng. In this small test, a lot of different Windows events will be forwarded to Stackdriver. Starting the test, you can see both the memory and the CPU usage are quite low, with memory usage hovering around 23 megabytes, while the CPU usage is below 20%. To verify that this works, let's check the statistics information of syslog-ng. The written counter is increasing, so this is a good sign. In this short demonstration, syslog-ng could reach around 10,000 events per second. After switching over to Stackdriver, we can see that the logs are indeed here. We trust you found this brief video helpful. There are just a few things you can do to ensure you're optimizing performance with your syslog-ng and the Stackdriver feed. To get more information about syslog-ng log management solutions, go to syslog-ng.com [MUSIC PLAYING]