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

JSON extractor adds "." in field names of nested JSON objects #1841

Closed
the-Pretender opened this issue Feb 19, 2016 · 1 comment
Closed

JSON extractor adds "." in field names of nested JSON objects #1841

the-Pretender opened this issue Feb 19, 2016 · 1 comment
Assignees
Labels
Milestone

Comments

@the-Pretender
Copy link

@the-Pretender the-Pretender commented Feb 19, 2016

Problem description

JSON extractor adds "." in field names of nested JSON objects. This is a problem as it is not supported by elasticsearch 2.* hence the fields are missing.

Steps to reproduce the problem

  1. Create a Syslog TCP input and send a message containing {"test": {"foo":"bar"}}
  2. JSON extractor preview shows "desired" output, but field is never created.

Environment

  • Graylog Version: 2.0.0 alpha 3
  • Elasticsearch Version: 2.2.0
  • MongoDB Version: not applicable
  • Operating System: not applicable
@joschi
Copy link
Contributor

@joschi joschi commented Feb 19, 2016

@the-Pretender Thanks for reporting this. We've changed the default value for the JSON extractor in d07f06f but it seems that we forgot to update the front end part (https://github.com/Graylog2/graylog2-server/blob/2.0.0-alpha.3/graylog2-web-interface/src/components/extractors/extractors_configuration/JSONExtractorConfiguration.jsx#L27-L30).

@joschi joschi added this to the 2.0.0 milestone Feb 19, 2016
@joschi joschi added bug web labels Feb 19, 2016
@joschi joschi closed this in e4d1db4 Feb 19, 2016
@joschi joschi self-assigned this Feb 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants