Project

General

Profile

Feature #3615

Feature #2454: Advertise classad in case of glidein failure

Add failed glidein monitoring to the Frontend

Added by Igor Sfiligoi almost 7 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Parag Mhashilkar
Category:
Frontend Monitoring
Target version:
Start date:
08/26/2014
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Stakeholders:
Duration:

Description

Now that we have failure classads in the VO collector, the Frontend should monitor them.


Subtasks

Feature #6869: Frontend should log the failed classad statsClosedIgor Sfiligoi


Related issues

Related to GlideinWMS - Feature #5011: Frontend monitoring should also show what factory is doing with its requestsNew08/26/2014

Related to GlideinWMS - Bug #6899: Frontend fix_rrd not reliableClosed08/29/2014

History

#1 Updated by Burt Holzman almost 7 years ago

  • Target version set to v3_1

#2 Updated by Burt Holzman over 6 years ago

  • Target version changed from v3_1 to v3_x

#3 Updated by Igor Sfiligoi over 5 years ago

Separating static info logging (#6869) from RRD updates, since the amount of work to get them implemented is quite different.

#4 Updated by Igor Sfiligoi over 5 years ago

  • Category changed from Factory & Frontend Monitoring to Frontend Monitoring
  • Status changed from New to Feedback
  • Assignee changed from Igor Sfiligoi to Parag Mhashilkar
  • Target version changed from v3_x to v3_2_8

Code implemented in v3/3615.
Please review.

PS1: Abandoned #6869 since XML and RRD code are implemented together.
PS2: Fix-rrd functionality seems broken, so we need a fix for #6899 before pushing this in production, since it changes the RRD schema.

#5 Updated by Parag Mhashilkar about 5 years ago

  • Status changed from Feedback to Resolved

Merged to branch_v3_2 and master

#6 Updated by Parag Mhashilkar about 5 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF