[GH-ISSUE #1417] ElasticsearchFormatter: Force record values to be strings #592

New issue

Closed

opened 2026-03-04 02:16:14 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 02:16:14 +03:00

Owner

Originally created by @tomsommer on GitHub (Jan 7, 2020).
Original GitHub issue: https://github.com/Seldaek/monolog/issues/1417

Monolog version 2

ElasticsearchFormatter should force all records to be strings, since ElasticSearch will fail on field types mixing in an index.

It would also make sense to not allow deep arrays, basically flatten arrays and make them scalar.

Originally created by @tomsommer on GitHub (Jan 7, 2020). Original GitHub issue: https://github.com/Seldaek/monolog/issues/1417 Monolog version 2 ElasticsearchFormatter should force all records to be strings, since ElasticSearch will fail on field types mixing in an index. It would also make sense to not allow deep arrays, basically flatten arrays and make them scalar.

kerem

2026-03-04 02:16:14 +03:00

closed this issue
added the
Bug

Support
labels

kerem commented

2026-03-04 02:16:15 +03:00

Author

Owner

@Seldaek commented on GitHub (May 11, 2020):

I don't think we can really do that without breaking BC.. It just means that currently you have to manage your context data carefully yourself.. The data provided by Monolog itself is consistently typed AFAIK. IMO this fact makes ElasticSearch generally speaking a poor choice for log storage but I can't choose what people use..

@Seldaek commented on GitHub (May 11, 2020): I don't think we can really do that without breaking BC.. It just means that currently you have to manage your context data carefully yourself.. The data provided by Monolog itself is consistently typed AFAIK. IMO this fact makes ElasticSearch generally speaking a poor choice for log storage but I can't choose what people use..

kerem referenced this issue

2026-03-04 03:11:27 +03:00

[PR #855] [CLOSED] Up latest master branch from Seldaek/monolog #1382