deblan/FOSElasticaBundle
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Update logger documentation based on configuration change

Browse source
This commit is contained in:
Tim Nagel 2014-03-26 12:40:27 +11:00
parent 9f27c1dade
commit 38b4074745
1 changed files with 5 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
Resources/doc/cookbook/logging.md
View file

@ -5,8 +5,10 @@ By default, FOSElasticaBundle sets a logger against each Elastica client configu
logs all information sent to and received from Elasticsearch. This can lead to large
memory usage during population or reindexing of an index.
FOSElasticaBundle provides an option to disable a logger by setting the property on the
client configuration to false:
By default FOSElasticaBundle will only enable a logger when debug mode is enabled, meaning
in a production environment there wont be a logger enabled. To enable a logger anyway, you
can set the logger property of a client configuration to true or a service id of a logging
service you wish to use.
```yaml
# app/config/config.yml
@ -14,12 +16,9 @@ fos_elastica:
clients:
default:
host: example.com
logger: false
logger: true
```
It may be desirable to set this configuration property to `%kernel.debug%`, which would
only switch the logging capabilities of FOSElasticaBundle on when debugging is enabled.
Custom Logger Service
---------------------