You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to do some refactoring to change the config and event schema before the Auditbeat GA release. Auditbeat reuses Metricbeat's framework, and the framework's orientation around metrics is visible to the Auditbeat user, but it shouldn't be.
Goals
Simplify configuration for the end-user
Modules should map clearly to events the users want to monitor.
Divorce from the Metricbeat event data model
The metricset namespace isn't necessary here.
Abstract the data source from module
Users shouldn't need to know how the data is collected
If needed an advanced user should be able to control what data sources are used.
For example have a module for monitoring what processes are running or what sockets are active rather than a module oriented around a data source like the kernel's audit framework or eBPF.
Provide specialized dashboards for each module.
Steps
Modify the Metricbeat framework to allow for customization of the event builder (the builder is responsible for adding the metricset field to all events).
Reorganize the config to allow for modules without "metricsets".
Rename the existing audit/kernel metricset to the auditd module. (As we add modules I expect this to be used less.)
Rename the existing audit/file metricset to file_integrity.
Sample Configs
Note the removal of metricsets: [] and the removal of the module name prefixes from the config options.
Separation of data source from modules reminds me a lot of prospectors types and modules in Filebeat. Would be great to sync up on this one for Filebeat to make sure the configuration options are similar.
This changes the audit.file and audit.kernel metricsets into modules
named file_integrity and auditd, respectively. This requires existing
users to update their configuration.
The dashboards need to be updated to account for these changes.
Closeselastic#5422 (see the issue for more details)
This changes the audit.file and audit.kernel metricsets into modules
named file_integrity and auditd, respectively. This requires existing
users to update their configuration.
The dashboards need to be updated to account for these changes.
Closes#5422 (see the issue for more details)
Update: See Breaking Changes in Auditbeat 6.2 for info about how to upgrade from an earlier version.
We want to do some refactoring to change the config and event schema before the Auditbeat GA release. Auditbeat reuses Metricbeat's framework, and the framework's orientation around metrics is visible to the Auditbeat user, but it shouldn't be.
Goals
metricset
namespace isn't necessary here.Steps
metricset
field to all events).auditd
module. (As we add modules I expect this to be used less.)file_integrity
.Sample Configs
Note the removal of
metricsets: []
and the removal of the module name prefixes from the config options.The text was updated successfully, but these errors were encountered: