arc-blahp-logger(8)
π arc-blahp-logger(8) π
okay bestie, welcome to the NorduGrid Toolkit corner of the manual, this one's arc-blahp-logger and she is serving accounting realness π
β¨ NAME β¨
arc-blahp-logger β an ARC authplugin that stores BLAH accounting logs about jobs that have FINISHED π
πΈ DESCRIPTION πΈ
so basically: ARC BLAH logger is an authplugin whose whole job is to stash info about FINISHED jobs into log files, the kind that the BLAH parser eats for breakfast π. Once those logs exist, APEL/DGAS client tools can pick them up and yeet your accounting info wherever it needs to go. it's giving "quietly doing the most important background work" energy fr fr π
π¦ SYNOPSIS π¦
arc-blahp-logger -I <jobID> -U <user> -P <proxy file> -L <job status file> [-c <ceid prefix>] [-p <log prefix> ] [-d <log level>] [-i]
π OPTIONS π
-IjobID β the A-REX job identifier. the name tag of the job, if you will π·οΈ-Uuser β the local account that owns the job's files and processes-Puser proxy β path to the user's proxy certificate file, so we can pull the VOMS membership info out of it π-Ljob status file β the A-REX jobstatus.localfile, which is holding extra lore about the job (like the LRMS id) π-cceid prefix β the prefix used to generate the CE ID, in accordance with GLUE1.3 publishing-plog prefix β where the logs live and what their filename prefix is. default is/var/log/arc/accounting/blahp.logποΈ-dloglevel β the logging level, and it runs from0(ERROR) all the way up to5(DEBUG)-iβ ignore failed jobs. heads up tho: the default is to publish them, so if you don't pass this, the failed ones go in the log too π
π§ ENABLING PLUGIN IN A-REX CONFIGURATION π§
to make this whole thing pop off, you need to add the BLAH logger plugin as a handler for the FINISHED state, like this:
authplugin="FINISHED timeout=10,onfailure=pass /usr/libexec/arc/arc-blahp-logger -I %I -U %u -L %C/job.%I.local -P %C/job.%I.proxy"
that's the whole vibe check. add it, and you're in business β¨
π CONFIGURATION π
ngl there's no special plugin configuration happening here β it's literally just "pass the correct options" and you're done. no secret handshake, no hidden config file. periodt π
by default the BLAH log gets written to /var/log/arc/accounting/blahp.log-YYYYMMDD. the log prefix (that's the part without the -YYYYMMDD) can be redefined with the optional -p option π
the CE ID is generated automatically and its format is host.fqdn:2811/nordugrid-torque-queue, in accordance with GLUE1.3 publishing. the queue gets added at runtime anyway, but the prefix can be redefined with the -c option. and yes, you should add this option in case of LRMS π
and if you wanna debug the logger's execution, just add the -d 5 option and you'll see all the ARC logger output from all the subsystems it uses. it's a lot. it's iconic. it's a firehose π₯
π AUTHOR π
Andrii Salnikov <manf at grid dot org dot ua>
and that's the whole page bestie, no cap π
this was brought to you by the NorduGrid 7.2.0 girlies, dated 2014-02-20 β yeah she's a classic, she's been slaying since 2014 and she's not stopping π¦π
β¨
π¦ where this page comes from
- epel 10: nordugrid-arc7-arex 7.2.0-1.el10_3 Β· Apache-2.0 AND MIT
- epel 9: nordugrid-arc7-arex 7.2.0-1.el9 Β· Apache-2.0 AND MIT
- fedora 43: nordugrid-arc-arex 7.2.0-1.fc43 Β· Apache-2.0 AND MIT
- fedora 44: nordugrid-arc-arex 7.2.0-1.fc44 Β· Apache-2.0 AND MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms