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

[BUG] JSON parse error #6513

Closed
diegargon opened this issue Apr 17, 2024 · 5 comments
Closed

[BUG] JSON parse error #6513

diegargon opened this issue Apr 17, 2024 · 5 comments
Labels
bug Something isn't working needs more info Requires more information from poster

Comments

@diegargon
Copy link

diegargon commented Apr 17, 2024

Describe the bug

Got this error

JSON.parse: expected ',' or '}' after property value in object at line 1 column 13008 of the JSON data

HttpFetchError@http://172....:5601/7326/bundles/core/core.entry.js:15:184257
fetchResponse@http://172...:5601/7326/bundles/core/core.entry.js:

After split the indexer the error was related to logs about windows-secuirty-mitigation (Windoes Event forward)

winlogbeat->logstash->opensearch

The rest works fine.

Related component

Indexing

To Reproduce

Loading
Discover->windows-security-mitigation logs

Expected behavior

No error.

Additional Details

Opensearch v 2.12.0

@diegargon diegargon added bug Something isn't working untriaged labels Apr 17, 2024
@dblock
Copy link
Member

dblock commented Apr 17, 2024

@diegargon Where are you getting this error? In winglogbeat? In logstash? How does one reproduce it?

@peternied
Copy link
Member

[Triage - attendees 1 2 3 4 5 6]

@opensearch-project/admin Please transfer this to the OpenSearch Dashboards repository

@bbarani bbarani transferred this issue from opensearch-project/OpenSearch Apr 17, 2024
@diegargon
Copy link
Author

diegargon commented Apr 17, 2024

@diegargon Where are you getting this error? In winglogbeat? In logstash? How does one reproduce it?

as i already wrote searching with "Discovery" (opensearch-dashboard) and selecting that particular indexer/logs

If I empty the log, I might be able to see some log, but there's a specific event (that i cannot be seen) causing the failure shortly after.

@kavilla
Copy link
Member

kavilla commented Apr 23, 2024

@diegargon, we have added some fixes related to this in 2.13. Could you verify if you are still experiencing this issue?

Here is the PR for the fix: #6253.

Will close this issue for now, if upgrading and if you find that this issue still exists please re-open and it will automatically add the untriaged label for visibility purposes.

Thank you!

@kavilla kavilla added needs more info Requires more information from poster and removed untriaged labels Apr 23, 2024
@kavilla kavilla closed this as completed Apr 23, 2024
@diegargon
Copy link
Author

@kavilla Seems fixed (fast check), thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs more info Requires more information from poster
Projects
None yet
Development

No branches or pull requests

4 participants