Feature #5012
Factory monitoring to display sites with issues
0%
OSG
Description
We need easy way to identify the sites that have held glideins. Currently, a single site have multiple entries in the factory config. We need a mechanism to aggregate all the held glideins associated with an entry and if the number is above certain threshold, the site should be flagged in the monitoring.
History
#1 Updated by Parag Mhashilkar over 7 years ago
- Stakeholders updated (diff)
#2 Updated by Igor Sfiligoi over 7 years ago
I guess this related to one of my requests... so let me correct it, as it is not what I meant.
The above description mixes two problems:- Aggregation of information from multiple entries going into a single (logical) site
And for this I would like to have the full blown "standard monitoring" web pages - The impossibility of currently monitoring the scale of problems we have in the factory;
for this one I would like to have a counter that tells me how many of the entries are problematic/broken
and the entry hitting the held limit is just one of the conditions I would like to have monitored this way
I leave it up to Parag to decide how to proparly split the issue into two separate tickets.
Thanks,
Igor
#3 Updated by Igor Sfiligoi over 7 years ago
Actually... the ability to group multiple entries is already there.
Through the monitorgroup field... a little annoying due to repeated info, but quite powerful, actually.
#4 Updated by Burt Holzman over 7 years ago
- Assignee set to Marco Mambelli
#5 Updated by Parag Mhashilkar over 5 years ago
- Stakeholders updated (diff)
#6 Updated by Marco Mambelli almost 3 years ago
- Target version changed from v3_2_x to v3_4_x
#7 Updated by Marco Mambelli over 2 years ago
- Target version changed from v3_4_x to v3_5_x
#8 Updated by Marco Mambelli over 1 year ago
- Target version changed from v3_5_x to v3_6_x
#9 Updated by Marco Mascheroni 6 months ago
- Stakeholders updated (diff)
Removing CMS from the Stakeholder list since this is no more relevant
#10 Updated by Marco Mambelli 18 days ago
- Target version changed from v3_6_x to v3_7_x