[Auditbeat] Change module configuration from "metricsets" to "datasets"#10018
[Auditbeat] Change module configuration from "metricsets" to "datasets"#10018cwurm merged 3 commits intoelastic:masterfrom
Conversation
|
Pinging @elastic/secops |
|
So far I kept |
|
The data Auditbeat reports are not “metrics”. “Audit events” is probably
the most accurate term. So it would be weird if its sub-modules would be
called “metricsets” in the user-facing configuration and documentation. It
leaks its Metricbeat roots that the user should not see.
“Datasets” is the more generic term that we arrived at in the SecOps team.
Metricbeat and Filebeat can keep their terms, this is just for Auditbeat.
Since with this change the code would overwrite the MetricSets field with
the contents of `datasets`, only `datasets` will work for Auditbeat.
…On Fri, 11 Jan 2019 at 15:51 Nicolas Ruflin ***@***.***> wrote:
So far I kept fileset and metricset around as we still had it in the
config and I thought we keep it (for example #9922
<#9922>). Could you share a bit more
background on this change? I assume for auditbeat it would mean both
options work?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#10018 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAqZRfc3mWk25WnfK_BkqpKgaYHS6yPBks5vCLMbgaJpZM4Z7hz1>
.
|
|
This is then a breaking change I assume and all users have to change their config for 7? This needs a changelog entry then. One other thing I worry about is that we have afterwards 2 different "values" of dataset. On the event side the |
Auditbeat doesn't have any metricsets at the moment, so if we can get this change in for 6.6 we would not have a breaking change.
Personally, I think this is ok, and actually preferable to the situation where it's called |
|
Ok, SGTM for the dataset change. |
tsg
left a comment
There was a problem hiding this comment.
Code change LGTM. I'd wait for a review from @andrewkroh as well, to ACK the approach.
…s" (elastic#10018) Changes the Auditbeat system module configuration to use "datasets" rather than "metricsets" to configure its sub-modules: ``` - module: system datasets: - host - process [...] ``` (cherry picked from commit e42ccb4)
…s" (elastic#10018) Changes the Auditbeat system module configuration to use "datasets" rather than "metricsets" to configure its sub-modules: ``` - module: system datasets: - host - process [...] ``` (cherry picked from commit e42ccb4)
Since elastic/beats#10018, the Auditbeat System module uses `datasets` instead of `metricsets` to configure its sub-modules. This reflects that change and fixes the [current CI failures](https://beats-ci.elastic.co/job/elastic+beats-tester+master/242/) for beats-tester on Windows.
Follow up to #10018. Changes the Auditbeat system module documentation to say dataset rather than metricset in all places. No Go code changes.
Follow up to elastic#10018. Changes the Auditbeat system module documentation to say dataset rather than metricset in all places. No Go code changes. (cherry picked from commit 0a4a349) (cherry picked from commit 2fa9541ee595153a393b3adf2e33a44f23b7a0f6)
Follow up to elastic#10018. Changes the Auditbeat system module documentation to say dataset rather than metricset in all places. No Go code changes. (cherry picked from commit 0a4a349) (cherry picked from commit 2fa9541ee595153a393b3adf2e33a44f23b7a0f6)
…tion from "metricsets" to "datasets" (elastic#10050) Cherry-pick of PR elastic#10018 to 6.6 branch. Original message: Changes the Auditbeat system module configuration to use "datasets" rather than "metricsets" to configure its sub-modules: ``` - module: system datasets: - host - process [...] ```
…dataset" in docs (elastic#10106) Cherry-pick of PR elastic#10101 to 6.6 branch. Original message: Follow up to elastic#10018. Changes the Auditbeat system module documentation to say `dataset` rather than `metricset` in all places. No Go code changes.
This changes the Auditbeat system module configuration to use "datasets" rather than "metricsets" to configure its sub-modules:
It simply overwrites the
MetricSetsfield in the default Metricbeat configuration with the value of thedatasetsconfiguration.@andrewkroh We talked about the difficulty of making changes to
go-ucfgor to the Metricbeat code. Turns out there is no need to change anything undermetricbeat/, so I think this might be ok? What do you think? I think in the long term we might still want to change to a fileset-like configuration, but for now this would avoid having a mix of "dataset" and "metricset" in anything user-facing, i.e. documentation or configuration.Follow-up: