How can we analyze the performance impact of the audit daemon?

Solution Verified - Updated -

Issue

  • How can we see the system call overhead?

  • Is there a way to measure the impact of the Red Hat supported audit daemon rules?

  • Can we measure system calls per minute or per second in some way?

  • For example, if audit daemon is monitoring the "fopen" system call, would we be able to determine that the system call takes 10%, 15%, longer to execute then it would without the audit rule?

Environment

  • Red Hat Enterprise Linux (All versions)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content