Project

General

Profile

Bug #9711

better logging

Added by Dennis Box over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
07/22/2015
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

/var/log/jobsub/error.log is still fairly unusable for operations. It is really a developers log, with verbosity set to max. It should honor a verbosity level or debug level setting in a config file.

Talking to operations people, they are mostly interested in
1) user a did jobsub_client command b from machine c at time d
2) result of 1) -> success or failure, minimal response from success and verbose from failure.

The error log should probably just have the above at minimum verbosity level, and its current spew state at max verbosity.

History

#1 Updated by Parag Mhashilkar over 5 years ago

  • Target version changed from v1.1.5 to v1.1.6

#2 Updated by Dennis Box over 5 years ago

  • Status changed from New to Feedback

see branch 9711. I don't really think feedback is needed from developers here, more so from operations. Two new logs created, 'condor_commands.log' and submit.log. Both log severity so they are grepable for ERROR

#3 Updated by Dennis Box over 5 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF