Project

General

Profile

Actions

feature request #6249

closed

better logging strategy

Added by Andreas Kohlbecker over 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Highest
Category:
cdmlib-remote
Target version:
Start date:
Due date:
% Done:

50%

Estimated time:
Severity:
major

Description

The cdmlib-remote instances in a cdm-server should not create individual logs per instance. It is more suitable if all instances are writing into the same log file which is out.log in case of the cdm-server. An instance should add its instane name to each line in the logfile so that it is possible to filter the log entries based on this instance name. A line in the logfile could look like:

[col] 2016-12-06 17:04:02,622 INFO [eu.etaxonomy.cdm.common.monitor.DefaultProgressMonitor] - 83.89831% done (Completed Task: Update proParte)

whereas [col] is the instance name part


Related issues

Related to EDIT - bug #6287: Rolling cdmserver.log file only contains entries from startup phaseDuplicateAndreas Kohlbecker

Actions
Related to EDIT - bug #7085: cdmserver logfiles getting too big, use RollingFileAppender ClosedAndreas Kohlbecker

Actions
Actions #1

Updated by Andreas Kohlbecker about 7 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 50
Actions #2

Updated by Andreas Kohlbecker about 7 years ago

  • Description updated (diff)
Actions #3

Updated by Andreas Kohlbecker about 7 years ago

  • Related to bug #6287: Rolling cdmserver.log file only contains entries from startup phase added
Actions #4

Updated by Andreas Kohlbecker about 7 years ago

  • Status changed from Resolved to Closed
Actions #5

Updated by Andreas Kohlbecker almost 4 years ago

  • Related to bug #7085: cdmserver logfiles getting too big, use RollingFileAppender added
Actions

Also available in: Atom PDF