Thomas Bechtold add4794120 Don't fail if sqlalchemy driver fails to initialize ... Given that the driver is initialized during the service startup (eg. like Keystone, Nova, ...) a osprofiler driver failure has a huge impact on the service (when the driver fails, the whole service is not usable). We want to avoid that and just log error/exceptions but keep the services running. Change-Id: I5688f10364884a74b7eb44c0c8bda15730ccd424 Closes-Bug: 1819433		2019-03-19 13:12:45 +01:00
..
cmd	Filter traces that contain error/exception	2018-02-05 15:14:17 +07:00
drivers	Don't fail if sqlalchemy driver fails to initialize	2019-03-19 13:12:45 +01:00
hacking	Move hacking checks outside tests	2016-11-23 13:00:30 +05:30
tests	In case of an error, always add message	2018-12-16 15:48:15 +02:00
__init__.py	Remove old notifiers	2016-08-31 17:11:32 +03:00
_utils.py	When shortening span-ids, check if they're already short	2018-10-09 07:37:11 +03:00
exc.py	Add Log Insight driver	2016-11-07 15:30:52 +05:30
initializer.py	Filter traces that contain error/exception	2018-02-05 15:14:17 +07:00
notifier.py	Add backward compatible drivers structure	2016-07-04 18:47:01 +03:00
opts.py	opts: Fix invalid rST formatting	2018-06-26 04:02:01 +00:00
profiler.py	In case of an error, always add message	2018-12-16 15:48:15 +02:00
sqlalchemy.py	In case of an error, always add message	2018-12-16 15:48:15 +02:00
web.py	Make profiler.clean() public method	2018-06-27 12:26:55 +01:00