Skip to content

[Auditbeat] Change module configuration from "metricsets" to "datasets"#10018

Merged
cwurm merged 3 commits intoelastic:masterfrom
cwurm:system_config_datasets
Jan 14, 2019
Merged

[Auditbeat] Change module configuration from "metricsets" to "datasets"#10018
cwurm merged 3 commits intoelastic:masterfrom
cwurm:system_config_datasets

Conversation

@cwurm
Copy link
Copy Markdown
Contributor

@cwurm cwurm commented Jan 11, 2019

This changes the Auditbeat system module configuration to use "datasets" rather than "metricsets" to configure its sub-modules:

- module: system
  datasets:
    - host
    - process
    [...]

It simply overwrites the MetricSets field in the default Metricbeat configuration with the value of the datasets configuration.

@andrewkroh We talked about the difficulty of making changes to go-ucfg or to the Metricbeat code. Turns out there is no need to change anything under metricbeat/, 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:

  1. Change documentation and other places where "metricset(s)" is used

@cwurm cwurm added review needs_backport PR is waiting to be backported to other branches. Auditbeat SecOps labels Jan 11, 2019
@cwurm cwurm requested a review from andrewkroh January 11, 2019 14:11
@cwurm cwurm requested review from a team as code owners January 11, 2019 14:11
@elasticmachine
Copy link
Copy Markdown
Contributor

Pinging @elastic/secops

@ruflin
Copy link
Copy Markdown
Contributor

ruflin commented Jan 11, 2019

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). Could you share a bit more background on this change? I assume for auditbeat it would mean both options work?

@cwurm
Copy link
Copy Markdown
Contributor Author

cwurm commented Jan 11, 2019 via email

@ruflin
Copy link
Copy Markdown
Contributor

ruflin commented Jan 14, 2019

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 dataset is {module}.{metricset}, on the config side it's just what metricset was previously. Do you see this as confusing or ok?

@cwurm
Copy link
Copy Markdown
Contributor Author

cwurm commented Jan 14, 2019

This is then a breaking change I assume and all users have to change their config for 7?

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.

One other thing I worry about is that we have afterwards 2 different "values" of dataset. On the event side the dataset is {module}.{metricset}, on the config side it's just what metricset was previously. Do you see this as confusing or ok?

Personally, I think this is ok, and actually preferable to the situation where it's called dataset in the event, but metricset in the configuration.

@ruflin
Copy link
Copy Markdown
Contributor

ruflin commented Jan 14, 2019

Ok, SGTM for the dataset change.

Copy link
Copy Markdown
Contributor

@tsg tsg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code change LGTM. I'd wait for a review from @andrewkroh as well, to ACK the approach.

Copy link
Copy Markdown
Member

@andrewkroh andrewkroh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

@cwurm cwurm merged commit e42ccb4 into elastic:master Jan 14, 2019
cwurm pushed a commit to cwurm/beats that referenced this pull request Jan 14, 2019
…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)
@cwurm cwurm added v6.6.0 and removed needs_backport PR is waiting to be backported to other branches. labels Jan 14, 2019
@cwurm cwurm added the v6.7.0 label Jan 14, 2019
cwurm pushed a commit to cwurm/beats that referenced this pull request Jan 14, 2019
…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)
cwurm pushed a commit that referenced this pull request Jan 14, 2019
…om "metricsets" to "datasets" (#10050)

Cherry-pick of PR #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
    [...]
```
cwurm pushed a commit that referenced this pull request Jan 15, 2019
…om "metricsets" to "datasets" (#10051)

Cherry-pick of PR #10018 to 6.x 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
    [...]
```
cwurm pushed a commit to elastic/beats-tester that referenced this pull request Jan 16, 2019
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.
cwurm pushed a commit that referenced this pull request Jan 16, 2019
Follow up to #10018.

Changes the Auditbeat system module documentation to say dataset rather than metricset in all places. No Go code changes.
cwurm pushed a commit to cwurm/beats that referenced this pull request Jan 16, 2019
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)
cwurm pushed a commit to cwurm/beats that referenced this pull request Jan 16, 2019
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)
cwurm pushed a commit that referenced this pull request Jan 16, 2019
…" in docs (#10106)

Cherry-pick of PR #10101 to 6.6 branch. Original message: 

Follow up to #10018.

Changes the Auditbeat system module documentation to say `dataset` rather than `metricset` in all places. No Go code changes.
cwurm pushed a commit that referenced this pull request Jan 16, 2019
…" in docs (#10105)

Cherry-pick of PR #10101 to 6.x branch. Original message: 

Follow up to #10018.

Changes the Auditbeat system module documentation to say `dataset` rather than `metricset` in all places. No Go code changes.
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…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
    [...]
```
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants