> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/english-v14/documentation/alarme-regeln-und-eskalationen/eskalationen/notification-provider/job-diagnostic.md).

# Job diagnostics

## What is the purpose of the *Job Diagnostics*?

The *Job Diagnostics* in *Eliona* serve for the detailed analysis and monitoring of the processing of *Notifications*. Here you can see which *Notifications* were triggered, through which providers they were escalated, and to whom they were sent. You also get insight into the status and history of the respective *Notification*-jobs.

With the *Job Diagnostics* you can:

* Monitor the delivery process of a *Notification* monitor.
* Trace escalation chains and recipients.
* Detect problems in delivery or processing at an early stage.
* Information about repeated *Notifications* and their duration.

This function is particularly helpful for administrators and operators to check the operation of the *Notification*-system and ensure that alerts and messages are forwarded properly.

***

## Open job diagnostics

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/5v9mV0Zyrn457y2rXPXq/Job%20Dagnostics.png" alt=""><figcaption></figcaption></figure></div>

* Open the menu item **Engineering \[A]**\
  ▷ The "Engineering" workspace opens.
* Click on **\[B] Notification providers**\
  ▷ The "Notifications providers" menu opens

  ▷ You will see a list of the available notification providers.
* To get to the **Job diagnostics** click on **\[C] " Show job diagnostic"**

***

## **The job diagnostics page**

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/33TxXRd6FLqAFewbNVet/Job%20Dagnostics%20(1).png" alt=""><figcaption></figcaption></figure></div>

<table data-full-width="true"><thead><tr><th width="92"></th><th width="127"></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>ID</td><td>The ID of the notification</td></tr><tr><td><strong>[B]</strong></td><td>Function</td><td>Which notification provider was used for escalation.</td></tr><tr><td><strong>[C]</strong></td><td>Recipient</td><td>To whom it was escalated.</td></tr><tr><td><strong>[D]</strong></td><td>Start</td><td>When the notification started.</td></tr><tr><td><strong>[E]</strong></td><td>Created</td><td>When the notification was triggered.</td></tr><tr><td><strong>[F]</strong></td><td>Delivered by</td><td>Who created the notification.</td></tr><tr><td><strong>[G]</strong></td><td>Status</td><td>The status of the notification.</td></tr><tr><td><strong>[H]</strong></td><td>Details</td><td>The details can be expanded; here you can see from which alert or which ticket the notification was triggered. You can also see when the last notification of this alert was sent, how often it was repeated, and how long it took.</td></tr><tr><td><strong>[I]</strong></td><td>Search</td><td>Here you can filter the notifications by various criteria.</td></tr><tr><td><strong>[J]</strong></td><td>More options</td><td>Click here to <strong>[K]</strong> open</td></tr><tr><td><strong>[K]</strong></td><td>Go to</td><td>Here you can go directly to the alert or ticket that triggered this notification</td></tr><tr><td><strong>[L]</strong></td><td>Page settings</td><td>Set here how many jobs you want to see or jump to the next or previous page.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.buildings.ability.abb/collection/english-v14/documentation/alarme-regeln-und-eskalationen/eskalationen/notification-provider/job-diagnostic.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.