Re: [HTCondor-users] getting metrics from collector

[Rita <rmorgan466@xxxxxxxxx>]

wanted to avoid condor_q but seems like no choice.

On Tue, Jul 26, 2022 at 3:13 AM Beyer, Christoph <christoph.beyer@xxxxxxx> wrote:

Hi Rita,

these sound like jobclassadd values, use condor_q & condor_history to query ....

Best Christoph


--
Christoph Beyer
DESY Hamburg
IT-Department

Notkestr. 85
Building 02b, Room 009
22607 Hamburg

phone:+49-(0)40-8998-2317
mail: christoph.beyer@xxxxxxx


----- UrsprÃngliche Mail -----
Von: Rita <rmorgan466@xxxxxxxxx>
An: HTCondor-Users Mail List <htcondor-users@xxxxxxxxxxx>
Gesendet: Tue, 26 Jul 2022 00:00:06 +0200 (CEST)
Betreff: [HTCondor-users] getting metrics from collector

I don't want to keep querying the scheduler because I know its inefficient.

I would like to get the following stats with condor_status:
1) User:how much memory they are requesting by job. Total aggregate is
fine, like user:<total request memory>
2) Same as #1, but for CPUs, request_cpus
3) Able to have a constraint for #1 and #2. My constraint would be idle vs
running jobs.



--
--- Get your facts first, then you can distort them as you please.--


_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/

--

--- Get your facts first, then you can distort them as you please.--