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

Create Migration Guide for 2.x to 5.x #1488

Closed
ruflin opened this issue Apr 26, 2016 · 5 comments
Closed

Create Migration Guide for 2.x to 5.x #1488

ruflin opened this issue Apr 26, 2016 · 5 comments
Labels

Comments

@ruflin
Copy link
Contributor

ruflin commented Apr 26, 2016

We have several backward compatibility breaks in 5.0. We should create a migration guide to make migration easier.

Please post below all the entries that should go into this migration guide.

@ruflin
Copy link
Contributor Author

ruflin commented Apr 26, 2016

Config Migration Topbeat

All config options of topbeat were moved under its own topbeat namespace. Topbeat will still work with the old configuration but this will be removed in the next major release. To adjust your configuration, you have to take the following steps:

  • Find input: in your topbeat.yml file with all its sub config options.
  • Replace input: with topbeat:

This will look similar to:

topbeat:
  period: 10
  ...

@ruflin
Copy link
Contributor Author

ruflin commented Apr 26, 2016

Config Migration Packetbeat

All config options of packetbeat were moved under its own packetbeat namespace. To keep packetbeat running, you must make the following modifications to your config file.

Option 1

  • Find the following 4 config options in your config file: interfaces, flows, procs, protocols
  • Indent all these config options including its sub configs with 2 spaces
  • Add packetbeat: on top of the config options

This will look as following:

packetbeat:
  interfaces:
    ...
  flows:
    ...
  procs:
    ...
  protocols:
    ...

Option 2

  • Find the following 4 config options in your config file: interfaces, flows, procs, protocols
  • Prepend all 4 options with packetbeat.

This will look as following:

packetbeat.interfaces:
  ...
packetbeat.flows:
  ...
packetbeat.procs:
    ...
packetbeat.protocols:
    ...

@andrewkroh
Copy link
Member

Another topic is changing the URL used in your APT and Yum repo config. I don't think we've published 5.x to any package repos yet, but we will and the URL will be different.

@tsg
Copy link
Contributor

tsg commented May 4, 2016

Move config settings from under beat to top level: #1570

@tsg tsg mentioned this issue May 4, 2016
14 tasks
tsg pushed a commit to tsg/beats that referenced this issue May 4, 2016
It doesn't do yaml parsing, just line by line string operations. This means
it is not able to transform any yaml syntax, but should work on the most
common cases.

On the plus side, it uses only python standard library modules and it keeps
the comments as in the original file. Related to elastic#1488.
andrewkroh pushed a commit that referenced this issue May 6, 2016
It doesn't do yaml parsing, just line by line string operations. This means
it is not able to transform any yaml syntax, but should work on the most
common cases.

On the plus side, it uses only python standard library modules and it keeps
the comments as in the original file. Related to #1488.
@monicasarbu monicasarbu added P1 and removed v5.0.0-rc1 labels May 19, 2016
@dedemorton dedemorton mentioned this issue Sep 7, 2016
50 tasks
@tsg
Copy link
Contributor

tsg commented Oct 22, 2016

This can be closed as we now have migration guides.

@tsg tsg closed this as completed Oct 22, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants