CONDOR_STATS(1)

🌸 CONDOR_STATS(1) 🌸

okay bestie, so this is a page from the HTCondor Manual and it's about condor_stats πŸ’–

✨ NAME ✨

condor_stats β€” it shows you the historical receipts of your HTCondor pool. like, what was everyone up to back then? this tool knows. πŸ‘‘

πŸ¦‹ SYNOPSIS πŸ¦‹

condor_stats [-f filename] [-orgformat ] [-pool
centralmanagerhostname[:portnumber]] [time-range ] query-type

πŸ’… DESCRIPTION πŸ’…

so condor_stats displays historic information about an HTCondor pool. based on the type of info you're asking for, a query gets sent to the condor_collector daemon, and whatever comes back gets shown on standard output. πŸŽ€

if you use the -f option, the info gets written to a file instead of standard output. and the -pool option lets you pull info from other pools instead of the local (default) one β€” it's giving ✨long distance relationship✨ but for collectors.

the condor_stats tool is used to query resource information (single or by platform), submitter and user information. if you don't specify a time range, the default query gives you info for the previous 24 hours. otherwise you can grab other time ranges, like the last specified number of hours, last week, last month, or a specified date range. so many options, we love a flexible queen 🫢

the info is displayed in columns separated by tabs. the first column always represents the time, as a percentage of the range of the query. so the first entry will have a value close to 0.0, and the last will be close to 100.0. if you use the -orgformat option, the time is displayed as number of seconds since the Unix epoch. the info in the rest of the columns depends on the query type. πŸ’€

lowkey important: logging of pool history must be enabled in the condor_collector daemon, otherwise no information will be available. no history, no vibes. 😭

one query type is required. if you specify multiple queries, only the last one takes effect. (iconic, but also watch out.)


⏰ TIME RANGE OPTIONS ⏰

  • -lastday β€” get info for the last day.
  • -lastweek β€” get info for the last week.
  • -lastmonth β€” get info for the last month.
  • -lasthours n β€” get info for the n last hours.
  • -from m d y β€” get info for the time since the beginning of the specified date. πŸ—“οΈ heads up though: a start date prior to the Unix epoch causes condor_stats to print its usage information and quit. she simply refuses. πŸ’…
  • -to m d y β€” get info for the time up to the beginning of the specified date, instead of up to now. a finish date in the future causes condor_stats to print its usage information and quit. no time travelers allowed, bestie. 🚫

πŸ” QUERY TYPE ARGUMENTS πŸ”

the query types that don't list all of a category need further specification, given by an argument. iykyk. ✨

  • -resourcequery hostname β€” a single resource query gives you info about a single machine. the info also includes the keyboard idle time (in seconds), the load average, and the machine state. main character machine energy. πŸ‘‘
  • -resourcelist β€” a query of a single list of resources, giving you a list of all the machines for which the condor_collector daemon has historic information within the query's time range. it's giving roll call πŸ“‹
  • -resgroupquery arch/opsys | "Total" β€” a query of a specified group, giving you info about a group of machines based on their platform (operating system and architecture). the architecture is defined by the machine ClassAd Arch, and the operating system is defined by the machine ClassAd OpSys. the string "Total" asks for info about all platforms. 🌈

the columns displayed are the number of machines that are unclaimed, matched, claimed, preempting, owner, shutdown, delete, backfill, and drained state. so many states, so little time.

  • -resgrouplist β€” queries for a list of all the group names for which the condor_collector has historic information within the query's time range.
  • -userquery email_address/submit_machine β€” query for a specific submitter on a specific machine. the info displayed includes the number of running jobs and the number of idle jobs. an example argument looks like this:
-userquery jondoe@sample.com/onemachine.sample.com
  • -userlist β€” queries for the list of all submitters for which the condor_collector daemon has historic information within the query's time range.
  • -usergroupquery email_address | "Total" β€” query for all jobs submitted by the specific user, regardless of the machine they were submitted from, or all jobs. the info displayed includes the number of running jobs and the number of idle jobs.
  • -usergrouplist β€” queries for the list of all users for which the condor_collector has historic information within the query's time range.

πŸŽ€ OPTIONS πŸŽ€

  • -f filename β€” write the info to a file instead of standard output. πŸ“
  • -pool centralmanagerhostname[:portnumber] β€” contact the specified central manager instead of the local one.
  • -orgformat β€” display the info in an alternate format for timing, which presents timestamps since the Unix epoch. this argument only affects the display of resoursequery, resgroupquery, userquery, and usergroupquery. ⏳

πŸ’€ EXIT STATUS πŸ’€

condor_stats exits with a status value of 0 (zero) upon success, and exits with the value 1 (one) upon failure. slay on success, sad girl hours on failure. 😭


πŸ‘‘ AUTHOR πŸ‘‘

HTCondor Team πŸ’œ


1990-2024, Center for High Throughput Computing, Computer Sciences Department, University of Wisconsin-Madison, Madison, WI, US. Licensed under the Apache License, Version 2.0.


okay that's the whole thing bestie, you're so welcome 🫢 this was the HTCondor Manual version, dated Sep 19, 2025 β€” go query something iconic. βœ¨πŸŽ€πŸ’…

πŸ“¦ where this page comes from