Feature #5011

Frontend monitoring should also show what factory is doing with its requests

Added by Parag Mhashilkar almost 7 years ago. Updated 22 days ago.

Frontend Monitoring
Target version:
Start date:
Due date:
% Done:


Estimated time:
(Total: 0.00 h)




Currently, frontend monitoring shows what it knows about the requests, how many resources have been provisioned and what the limits are. However it does not tell what factory is doing with the requests, how many glieins have been submitted etc. All this info is in the glideresource classad, we need to capture it in the rrds and make a monitoring page displaying this information. This is frontend equivalent of factory status now web page.


Feature #6868: Frontend should log what the factory is doing with its requestsClosedIgor Sfiligoi

Related issues

Related to GlideinWMS - Feature #3615: Add failed glidein monitoring to the FrontendClosed08/26/2014


#1 Updated by Igor Sfiligoi almost 7 years ago

We want both the "status now" page and the historical RRDs containing the factory stats (with proper visualization).

And the Web pages should allow for easy comparison between the requests and what was is happening in the factory.

#2 Updated by Parag Mhashilkar almost 7 years ago

  • Stakeholders updated (diff)

#3 Updated by Burt Holzman almost 7 years ago

  • Assignee set to Marco Mambelli

#4 Updated by Igor Sfiligoi about 6 years ago

Separated the writing the static information (#6868) from RRD updates, since the amount of work needed to achieve it is quite different.

#5 Updated by Igor Sfiligoi about 6 years ago

We actually don't have the information currently in memory.
The frontend never fetches the glidefactoryclient classads.

This also means that the numbers the FE publishes in the glideresource classads are not useful.
(they are totals across all requesting FEs for that entry)

BTW: Abandoning #6868, since XML and RRD monitoring is really closely correlated.

#6 Updated by Marco Mambelli over 2 years ago

  • Target version changed from v3_2_x to v3_4_x

#7 Updated by Marco Mambelli about 2 years ago

  • Target version changed from v3_4_x to v3_5_x

#8 Updated by Marco Mambelli 12 months ago

  • Target version changed from v3_5_x to v3_6_x

#9 Updated by Marco Mascheroni 22 days ago

  • Stakeholders updated (diff)

Removing CMS from the Stakeholder list since this is no more relevant

Also available in: Atom PDF