optimus logger Config [Jenkins]
4/16/2015 optimus-logger Config [Jenkins] http://build.bluejeansnet.com/view/ON-Prem/job/optimus-logger/configure 1/3 BJN BuildMaster | log out Back to Dashboard Status Changes Workspace 154/optimuslogger #10 10.5.9.154/optimuslogger #9 10.5.9.154/optimuslogger #8 10.5.9.154/optimuslogger #7 #6 10.5.9.154/optimuslogger #5 10.5.9.154/optimuslogger #4 10 10.5.9.154/optimuslogger #3 10.5.9.154/optimuslogger #2 10.5.9.154/optimuslogger RSS for all RSS for failures Project name optimuslogger Description [Raw HTML] Preview Discard0 码力 | 3 页 | 218.24 KB | 1 年前3Celery v5.0.1 Documentation
the task instance (self), just like Python bound methods: logger = get_task_logger(__name__) @task(bind=True) def add(self, x, y): logger.info(self.request.id) Bound tasks are needed for retries special logger is available named “celery.task”, you can inherit from this logger to automatically get the task name and unique id as part of the logs. The best practice is to create a common logger for all import get_task_logger logger = get_task_logger(__name__) @app.task def add(x, y): logger.info('Adding {0} + {1}'.format(x, y)) return x + y Celery uses the standard Python logger library, and the0 码力 | 2313 页 | 2.13 MB | 1 年前3Celery v5.0.2 Documentation
the task instance (self), just like Python bound methods: logger = get_task_logger(__name__) @task(bind=True) def add(self, x, y): logger.info(self.request.id) Bound tasks are needed for retries special logger is available named “celery.task”, you can inherit from this logger to automatically get the task name and unique id as part of the logs. The best practice is to create a common logger for all import get_task_logger logger = get_task_logger(__name__) @app.task def add(x, y): logger.info('Adding {0} + {1}'.format(x, y)) return x + y Celery uses the standard Python logger library, and the0 码力 | 2313 页 | 2.14 MB | 1 年前3Celery v5.0.0 Documentation
the task instance (self), just like Python bound methods: logger = get_task_logger(__name__) @task(bind=True) def add(self, x, y): logger.info(self.request.id) Bound tasks are needed for retries special logger is available named “celery.task”, you can inherit from this logger to automatically get the task name and unique id as part of the logs. The best practice is to create a common logger for all import get_task_logger logger = get_task_logger(__name__) @app.task def add(x, y): logger.info('Adding {0} + {1}'.format(x, y)) return x + y Celery uses the standard Python logger library, and the0 码力 | 2309 页 | 2.13 MB | 1 年前3Celery v5.0.5 Documentation
the task instance (self), just like Python bound methods: logger = get_task_logger(__name__) @task(bind=True) def add(self, x, y): logger.info(self.request.id) Bound tasks are needed for retries special logger is available named “celery.task”, you can inherit from this logger to automatically get the task name and unique id as part of the logs. The best practice is to create a common logger for all import get_task_logger logger = get_task_logger(__name__) @app.task def add(x, y): logger.info('Adding {0} + {1}'.format(x, y)) return x + y Celery uses the standard Python logger library, and the0 码力 | 2315 页 | 2.14 MB | 1 年前3[JavaSE实验] JDBC and MySQL
SQLException; import java.sql.Statement; import java.util.logging.Level; import java.util.logging.Logger; public class Version { public static void main(String[] args) { Connection con = println(rs.getString(1)); } } catch (SQLException ex) { Logger lgr = Logger.getLogger(Version.class.getName()); lgr.log(Level.SEVERE, ex.getMessage(), ex); con.close(); } } catch (SQLException ex) { Logger lgr = Logger.getLogger(Version.class.getName()); lgr.log(Level.WARNING, ex.getMessage()0 码力 | 23 页 | 2.52 MB | 1 年前3Celery 3.0 Documentation
the task instance (self), just like Python bound methods: logger = get_task_logger(__name__) @task(bind=True) def add(self, x, y): logger.info(self.request.id) Bound tasks are needed for retries special logger is available named “celery.task”, you can inherit from this logger to automatically get the task name and unique id as part of the logs. The best practice is to create a common logger for all import get_task_logger logger = get_task_logger(__name__) @app.task def add(x, y): logger.info('Adding {0} + {1}'.format(x, y)) return x + y Celery uses the standard Python logger library, and the0 码力 | 2110 页 | 2.23 MB | 1 年前3Celery v4.0.0 Documentation
the task instance (self), just like Python bound methods: logger = get_task_logger(__name__) @task(bind=True) def add(self, x, y): logger.info(self.request.id) Bound tasks are needed for retries special logger is available named “celery.task”, you can inherit from this logger to automatically get the task name and unique id as part of the logs. The best practice is to create a common logger for all import get_task_logger logger = get_task_logger(__name__) @app.task def add(x, y): logger.info('Adding {0} + {1}'.format(x, y)) return x + y Celery uses the standard Python logger library, and the0 码力 | 2106 页 | 2.23 MB | 1 年前3Celery 2.1 Documentation
executed locally in the client, and not by a worker. logfile The log file, can be passed on to get_logger() to gain access to the workers log file. See Logging. loglevel The current log level used. delivery_info Logging You can use the workers logger to add diagnostic output to the worker log: class AddTask(Task): def run(self, x, y, **kwargs): logger = self.get_logger(**kwargs) logger.info("Adding %s + %s" % (x User Guide Celery Documentation, Release 2.1.4 @task() def add(x, y, **kwargs): logger = add.get_logger(**kwargs) logger.info("Adding %s + %s" % (x, y)) return x + y There are several logging levels available0 码力 | 285 页 | 1.19 MB | 1 年前3Celery 2.1 Documentation
executed locally in the client, and not by a worker. logfile: The log file, can be passed on to get_logger() to gain access to the workers log file. See Logging. loglevel: The current log level used. delivery_info: can use the workers logger to add diagnostic output to the worker log: class AddTask(Task): def run(self, x, y, **kwargs): logger = self.get_logger(**kwargs) logger.info("Adding %s + %s" return x + y or using the decorator syntax: @task() def add(x, y, **kwargs): logger = add.get_logger(**kwargs) logger.info("Adding %s + %s" % (x, y)) return x + y There are several logging levels0 码力 | 463 页 | 861.69 KB | 1 年前3
共 1000 条
- 1
- 2
- 3
- 4
- 5
- 6
- 100