pg_jobmon

pj_jobmon allows database administrators to easily follow database operations and check out how one or more functions behave.

When dealing with a job failure or other error, pj_jobmon logs everything to that point and does not miss messages or details that might help the developer in fixing the issue.

This extension can be a real time saver in debugging problematic jobs or for testing new extensions or updates.

What is new in this release:

• Bugfix:
• Fixed show_running() to only match against non-idle queries when joining against pg_stat_activty. Still a chance of false result (see doc file), but much less likely now.

What is new in version 1.2.0:

• Bugfix:
• Fixed show_running() to only match against non-idle queries when joining against pg_stat_activty. Still a chance of false result (see doc file), but much less likely now.

What is new in version 1.1.0:

• Critical Bug Fix: Version 1.0 accidentally removed the creation of the trigger on the job_log table so that failing jobs would never cause check_job_status() to report a failed job. Jobs that were configured to run within a certain time period were still monitored for. This only affects new installations of pg_jobmon since 1.0. If you've upgraded from a previous version, the trigger is still working properly.
• Redesigned check_job_status() to return more detailed, and more easily filtered data on the current status of running jobs. Please check how your monitoring software used this function to ensure it can handle the new output format properly. Each problem job is returned in its own row instead of all results being returned in a single row. If a single row is still desired, the highest alert level job in alphabetical order of job_name is always returned first, so a LIMIT 1 can be used as an easy solution. More advanced filtering is now possible, though. See the updated pg_jobmon.md doc for some examples.
• Wrote pgTAP tests and some other custom tests to better validate future changes.

What is new in version 1.0.0:

• fail_job() can now take an optional second argument to set the final alert code level that the job should fail with in the job_log table. Allows jobs to fail with level 2 (WARNING) instead of only level 3 (CRITICAL). Default is level 3.
• New check_job_status() function that doesn't require an argument. Will automatically get longest threshold interval from job_check_config table if it exists and use that. Recommend using only this version of fuction from now on.
• check_job_status(interval) will now throw an exception if you pass an interval that is shorter than the longest job period that is being monitored. If nothing is set in the config table, interval doesn't matter, so will just run normally checking for 3 consecutive failures. Changed documentation to only mention the no-argument version since that's the safest/easiest way to use it.

What is new in version 0.4.5:

• Updated show_running() function to be compatible with PostgreSQL 9.2.
• Updated Makefile to allow setting of grep binary if needed during building.
• Created CHANGELOG file.

Requirements:

• PostgreSQL 9.1 or higher