Skip to content

Issues: logstash-plugins/logstash-filter-json

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.

Sign up for GitHub

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

26 Open 7 Closed
26 Open 7 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Possibility to parse with ALLOW_UNESCAPED_CONTROL_CHARS (or maybe more general way to configure parser features?) enhancement
#53 opened Jun 9, 2023 by Mekk
[ and ] in field names still cause parse failures bug
#51 opened Dec 19, 2022 by garethhumphriesgkc
The JSON filter can extract empty field names, which are then unusable by Logstash bug
#50 opened Jun 10, 2021 by nicolasreich
If source is empty, then warning that target is required
#48 opened Feb 23, 2021 by robin13
Log desapear if data.id is object
#47 opened Oct 1, 2020 by dateles
JsonParseFailure||Reason: Number of Characters in message field
#46 opened Jun 15, 2020 by shubhamgupta514
1
Add support for max_depth
#43 opened Oct 21, 2019 by tumluliu
json filter can not process data bigger then 4k
#42 opened Jun 10, 2019 by zhenglisai
6
json keys that look like references get dereferenced
#38 opened Dec 5, 2018 by bazzargh
6
Does not cope with extracting from multiple value logstash field array
#37 opened Sep 10, 2018 by antcodd
Add support for file path (as source)
#36 opened Feb 21, 2018 by make
Setting "target" and "source" to "message" silently drops events
#34 opened Sep 5, 2017 by jcmcken
5
logstash crash with "IndexError: string not matched" Exception
#33 opened Mar 3, 2017 by toopa2002
publish a new version to rubygems with the new skip_on_invalid_json option
#32 opened Jun 17, 2016 by joemiller
JSON Filter throws a warning (and fails to insert document) when object has a 'message' field
#31 opened Jun 9, 2016 by orweinberger
2
allow json target to be dynamic
#28 opened May 6, 2016 by surlypants
1
2
Add "jsonpath" support
#27 opened May 4, 2016 by xevgeny
Add prefix option
#19 opened Dec 22, 2015 by runningman84
2
Do not emit null fields or replace them with empty strings
#17 opened Nov 17, 2015 by mterron
1
Plugin crash due to invalid UTF-32 character
#15 opened Sep 28, 2015 by ThomasdOtreppe
2
A failed timestamp parse will leave a non LogStash::Timestamp in @timestamp bug
#14 opened Sep 7, 2015 by jsvd
1
problem parsing json arrays
#12 opened Jun 23, 2015 by necroscope
3
Deserialize array as Array object not ArrayList
#10 opened May 28, 2015 by felipegs
1
move field merging details from Filters::Json into Event
#9 opened May 17, 2015 by jordansissel
ensure source field is a string before attempting deserialization enhancement
#7 opened Apr 16, 2015 by colinsurprenant
2
ProTip! Add no:assignee to see everything that’s not assigned.