Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use the Beat version in the Ingest Node pipeline #3516

Merged
merged 1 commit into from
Feb 3, 2017

Conversation

tsg
Copy link
Contributor

@tsg tsg commented Feb 2, 2017

This adds the Beat version to the pipeline ID, which means that if
we change the pipeline between versions, the new version will be used
automatically. It also means that one can run different versions of the
same Beat and the pipelines won't override each other. The pipelines
are loaded automatically on the Beat start.

Part of #3159.

@tsg tsg added the review label Feb 2, 2017
@tsg tsg changed the title Use the Beat version in the Ingest Node pipeline a Use the Beat version in the Ingest Node pipeline Feb 2, 2017
@tsg tsg mentioned this pull request Feb 2, 2017
22 tasks
@@ -183,17 +183,17 @@ func TestGetProspectorConfigNginxOverrides(t *testing.T) {
assert.True(t, cfg.HasField("pipeline"))
pipelineID, err := cfg.String("pipeline", -1)
assert.NoError(t, err)
assert.Equal(t, "nginx-access-with_plugins", pipelineID)
assert.Equal(t, "nginx-access-with_plugins-5.2.0", pipelineID)
Copy link
Member

Choose a reason for hiding this comment

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

I would call the pipeline filebeat-5.2.0-nginx-access-with_plugins. This brings the following benefits:

  • No conflict with potential pipelines in the future from other beats
  • Assuming some can query for pipelines, to get / remove all filebeat pipelines filebeat-* can be used, to remove all 5.2 pipelines because everyting is using 5.3, filebeat-5.2.* can be used.

@tsg tsg force-pushed the filebeat_modules_pipeline_version branch 3 times, most recently from c5a25c2 to 4afb574 Compare February 3, 2017 08:45
This adds the Beat version to the pipeline ID, which means that if
we change the pipeline between versions, the new version will be used
automatically. It also means that one can run different versions of the
same Beat and the pipelines won't override each other. The pipelines
are loaded automatically on the Beat start.

Part of elastic#3159.
@tsg tsg force-pushed the filebeat_modules_pipeline_version branch from 4afb574 to 5a5b20d Compare February 3, 2017 11:27
@ruflin ruflin merged commit 42686b0 into elastic:master Feb 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants