# Job Monitoring Dashboard

The **FAFSA Job Scheduling & Monitoring Dashboards** provide real-time and historical insights into the performance, reliability, and efficiency of ISIR file processing workflows. These visualizations allow both IT teams and financial aid staff to monitor the operational health of automated job executions, troubleshoot failures, and optimize scheduling performance, all without needing direct access to Banner.

## Performance Overview

The first set of charts present a high-level view of job activity and success rates, helping financial aid and IT teams monitor processing health at a glance.

<figure><img src="/files/cO0iCgUrAbPTgbsrWpA8" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="Job Metrics Summary" %}
At the top of the dashboard, four key metrics summarize FAFSA job activity over the selected time period:

* Total Jobs Executed
* Successful Jobs
* Failed Jobs
* Jobs Retried

{% hint style="success" %}
This view supports quick operational assessments without needing to log into Banner.
{% endhint %}
{% endtab %}

{% tab title="Jobs by Day" %}
This chart displays the number of jobs processed each day (Mon–Sun), categorized by outcome:

* ✅ **Successful** (teal bars)
* ❌ **Failed** (yellow bars)

{% hint style="success" %}
Use this visualization to spot patterns such as high failure days or processing volume trends.
{% endhint %}
{% endtab %}

{% tab title="Success vs. Failure Distribution" %}
The **donut chart** to the right visualizes the overall **job outcome ratio** during the reporting window:

* Majority successful (teal)
* Minority failed (yellow)

{% hint style="success" %}
This quick snapshot supports SLA monitoring and system health reviews.
{% endhint %}
{% endtab %}
{% endtabs %}

### Detailed Execution Metrics & Job Logs

This section provides deeper insights into job duration, retry trends, and individual job details, enabling diagnostics and performance tuning.

<figure><img src="/files/DXVKsYr5bTqQUUOIjXXZ" alt=""><figcaption></figcaption></figure>

{% tabs %}
{% tab title="Average Duration per Stage" %}
A bar graph shows the average processing time (in seconds) for each phase of the workflow:

* Fetch (S3)
* Submit (Banner)
* Retrieve (Logs)

This helps identify stages that may be experiencing latency or require optimization.

{% hint style="info" %}
Pay close attention to spikes in max latency and an increasing error rate, especially during peak usage periods.
{% endhint %}
{% endtab %}

{% tab title="Retries & Queue Wait Time" %}
A line chart visualizes:

* Retry Count per day (yellow line)
* Average Wait Time before job processing begins (blue line)

These metrics reveal:

* Whether system issues are causing frequent retries
* How long jobs remain in queue before execution
  {% endtab %}

{% tab title="Recent Jobs Table" %}
This detailed table lists the most recent FAFSA job executions, including:

| Job ID      | Unique execution identifier       |
| ----------- | --------------------------------- |
| Date/Time   | Start time of the job             |
| Duration    | Total time taken for execution    |
| Stage Times | Time breakdown per stage          |
| Retries     | Number of retry attempts          |
| Status      | Final outcome (Success or Failed) |

Use this section to:

* Investigate failed jobs
* Compare performance across executions
* Review retry behavior
  {% endtab %}

{% tab title="FAFSA Jobs Pending Review" %}
At the bottom, the task queue displays pending job reviews, such as log investigations. This workflow enables exception handling, accountability, and compliance logging.
{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://processmaker.gitbook.io/higher-ed/fafsa-job-scheduling-and-monitoring/job-monitoring-dashboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.