Is it normal to have Symfony\Component\Debug\Exception\FatalErrorException exceptions in production? -
in our production logs can see exceptions symfony\component\debug\exception\fatalerrorexception
. have errors , fix them, bothers me "debug" classes.
we running in "prod" environment, normal have "debug" exceptions? or did misconfigure something?
having exceptions different having debug logging enabled.
basically logger
service available in container
. can use add important information code executed. wise have different logging configurations per environment. prod
environment example not have log 404 errors, maybe want log on test
environments? can exclude in config_prod.yml
. see: http://symfony.com/doc/current/cookbook/logging/monolog_regex_based_excludes.html
aside of actual logging, monolog
can send emails if threshold has been reached. on prod
can let monolog
send emails action_level: critical
, test
can more emails more info action_level: error
. setting level
can set minimum level log message should included in email. see http://symfony.com/doc/current/cookbook/logging/monolog_email.html
other recipes logging can found at: http://symfony.com/doc/current/cookbook/logging/index.html
to @ debug
parameter , exception
, symfony behaves differently debugging enabled. standard applications web toolbar , profiler enabled, , if exception thrown, symfony shows exception page. basically, way more data collected in debug
. if debug disabled, logger
still in place though. exceptions can occur, because result of uncaught application behavior (read: bugs). i'd advise use logger wisely emails contain sufficient information debug these exceptions.
Comments
Post a Comment