Speed up your IBM Power servers like never before. In IBM Power System environments, processing time is costly and is measured in work units. A CPU hog on any Linux server can become expensive. Under-provisioned systems react slowly on queries from business applications, which then cause undesired end user or processing delays. As IBM Power servers typically run business critical workloads, response time and availability is key.
eBPF tracing is a broad and deep subject, and can be a bit daunting at first sight. However, when Brendan Gregg issued the dictum “Perhaps you’d like a new year’s resolution: learn eBPF!”, I figured it was as good a time as any to do something fun with it. Here at Circonus, we’ve talked about eBPF previously, so I had a starting point to look for an interesting problem to solve.
NOTE: This is part 2 of a post on how to monitor your server. For pre-requisites and how to monitor a windows-based server, read the earlier blog post.
This recipe is similar to the previous rsyslog + Redis + Logstash one, except that we’ll use Kafka as a central buffer and connecting point instead of Redis. You’ll have more of the same advantages.
XpoLog 7 brings your data into a new age of log analysis and management. While the industry is focused on developing advanced search abilities and simplifying log analysis, nobody has been able to resolve the persistent issues of the long, complex and tedious deployments. Up until today! XpoLog 7 is proud to offer full automation of the entire log management lifecycle!
The Linux Audit framework is a kernel feature (paired with userspace tools) that can log system calls. For example, opening a file, killing a process or creating a network connection. These audit logs can be used to monitor systems for suspicious activity.
