starred/monolog
1
0
Fork 0
mirror of https://github.com/Seldaek/monolog.git synced 2026-04-26 08:05:53 +03:00
Code Issues 31 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #344] JsonFormatter doesn't put new line at end of entry #116

New issue
Closed
opened 2026-03-04 02:12:19 +03:00 by kerem · 2 comments
kerem commented 2026-03-04 02:12:19 +03:00
Owner
Copy link

Originally created by @xiankai on GitHub (Mar 27, 2014).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/344

I'm using the JsonFormatter in conjunction with the StreamHandler - but my log file ends up as a single giant line of JSON since I'm only adding one entry at a time and the formatter doesn't add a line break at the end as opposed to the LineFormatter.

Would it make sense to add a line break at the end or would it somehow corrupt handlers that expect strict JSON?

Originally created by @xiankai on GitHub (Mar 27, 2014). Original GitHub issue: https://github.com/Seldaek/monolog/issues/344 I'm using the JsonFormatter in conjunction with the StreamHandler - but my log file ends up as a single giant line of JSON since I'm only adding one entry at a time and the formatter doesn't add a line break at the end as opposed to the LineFormatter. Would it make sense to add a line break at the end or would it somehow corrupt handlers that expect strict JSON?
kerem 2026-03-04 02:12:19 +03:00
  • closed this issue
  • added the
    Feature
         label
kerem commented 2026-03-04 02:12:20 +03:00
Author
Owner
Copy link

@Seldaek commented on GitHub (Mar 27, 2014):

I don't think it would be a problem no. We already have something to do this for batch formatting, so I think it wouldn't hurt to also do it for the single-record formatting. I don't see what could be affected, but as a safety maybe it could be added as an optional constructor argument so it's possible to disable the newline if needed.

<!-- gh-comment-id:38799558 --> @Seldaek commented on GitHub (Mar 27, 2014): I don't think it would be a problem no. We already have something to do this for batch formatting, so I think it wouldn't hurt to also do it for the single-record formatting. I don't see what could be affected, but as a safety maybe it could be added as an optional constructor argument so it's possible to disable the newline if needed.
kerem commented 2026-03-04 02:12:20 +03:00
Author
Owner
Copy link

@Seldaek commented on GitHub (Apr 20, 2014):

The JsonFormatter adds a newline by default now

<!-- gh-comment-id:40898909 --> @Seldaek commented on GitHub (Apr 20, 2014): The JsonFormatter adds a newline by default now
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
esfix
2.x
1.x
3.10.0
2.11.0
3.9.0
3.8.1
3.8.0
2.10.0
3.7.0
3.6.0
2.9.3
3.5.0
2.9.2
3.4.0
3.3.1
2.9.1
3.3.0
2.9.0
3.2.0
2.8.0
3.1.0
2.7.0
1.27.1
3.0.0
2.6.0
3.0.0-RC1
2.5.0
2.4.0
1.27.0
2.3.5
2.3.4
2.3.3
2.3.2
2.3.1
2.3.0
1.26.1
2.2.0
1.26.0
2.1.1
1.25.5
2.1.0
1.25.4
2.0.2
1.25.3
2.0.1
1.25.2
1.25.1
1.25.0
2.0.0
2.0.0-beta2
2.0.0-beta1
1.24.0
1.23.0
1.22.1
1.22.0
1.21.0
1.20.0
1.19.0
1.18.2
1.18.1
1.18.0
1.17.2
1.17.1
1.17.0
1.16.0
1.15.0
1.14.0
1.13.1
1.13.0
1.12.0
1.11.0
1.10.0
1.9.1
1.9.0
1.8.0
1.7.0
1.6.0
1.5.0
1.4.1
1.4.0
1.3.1
1.3.0
1.2.1
1.2.0
1.1.0
1.0.2
1.0.1
1.0.0
1.0.0-RC1
Labels
Clear labels   
Bug

   
Documentation

   
Feature

   
Needs Work

   
Support

   
pull-request

Mirrored from GitHub Pull Request

No labels
Bug
Documentation
Feature
Needs Work
Support
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/monolog#116
No description provided.