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

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more