add unhandled events

[mathisloevenich]

Jobs that are handled at the current state:

• 000 (Job submitted)
• 001 (Job executing)
• 002 (Error in executable)
• 003 (Job was checkpointed)
• 004 (Job evicted from machine)
• 005 (Job terminated)
• 006 (Image size of job updated)
• 007 (Shadow exception)
• 008 (Generic log event) -> does not require handling
• 009 (Job aborted)
• 010 (Job was suspended)
• 011 (Job was unsuspended)
• 012 (Job was held)
• 013 (Job was released)
• 014 (Parallel node exectued)
• 015 (Parallel node terminated)
• 016 (POST script terminated)
• Job events between 016 an 022 are not documented and probably only for internal use case
• 022 (Remote system call socket lost)
• 023 (Remote system call socket reestablished)
• 024 (Remote system call reconnect failure)
• 025 (Grid Resource Back Up)
• 026 (Detected Down Grid Resource)
• 027 (Job submitted to grid resource)
• 028 (Job ad information event triggered.)
• 029 ()
• 030 ()
• 031 ()
• 032 ()
• 033 ()
• 034 ()
• 035 ()
• 036 ()
• 037 ()
• 038 ()
• 039 ()
• 040 ()

[mathisloevenich]

Have a look here: https://htcondor.readthedocs.io/en/latest/codes-other-values/job-event-log-codes.html

Not all jobs are handled yet and some of them might never be worth handeling/mentioning.

There is no api to know the data load of all the different events.

Therefore it would make sense to contact the team of htcondor for this:
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

I've been trying to find information about the JobEvent types in their database, but I could't find anything.