Clarify extractor compatibility #1831
Closed
Comments
FWIW, graylog-server is still using |
Well, maybe it should, but it doesn't. Exporting a newly created split and index extractor on graylog 2.0.0 alpha 2 yields the following:
The same extractor in 1.3.2:
In order to be able to import the latter to graylog 2.0.0 alpha 2,
|
bernd
added a commit
that referenced
this issue
Mar 16, 2016
The import/export format wrangling should be done on the server side instead of doing all of this in the browser. This is a minimal fix because refactoring this is too much at the moment. Fixes #1831
bernd
added a commit
that referenced
this issue
Mar 16, 2016
The import/export format wrangling should be done on the server side instead of doing all of this in the browser. This is a minimal fix because refactoring this is too much at the moment. Fixes #1831
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
From the mailing list, there is a report of a change in the extractors structure. Extractors exported from versions pre 2.0, had an
extractor_type
field, whereas in 2.0 that field is calledtype
.We should verify that we support old extractors or clarify that in the documentation, probably even notify plugin creators.
The text was updated successfully, but these errors were encountered: